this post was submitted on 16 Aug 2023
13 points (93.3% liked)

Firefox

17301 readers
132 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago
MODERATORS
 

As in title - is there a way to opt out from getting beta updates on Firefox Developer Edition? I don't want to constantly restart my browser, also it crashes a lot most likely because I'm always on beta version (currently on 117.0b8).

top 8 comments
sorted by: hot top controversial new old
[–] [email protected] 8 points 1 year ago (3 children)

Alright, I figured it out myself - you need to change app.update.channel in about:config to release. TIL that developer edition has its own update channel called 'aurora' which is even more experimental than 'beta'.

[–] Krafting 9 points 1 year ago (1 children)

This is the point of the dev edition, so web developpers can test out new features and breaking changes before new releases. Just use the normal firefox if you don't want that.

Or maybe I'm missing something?

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

Well, I wasn’t really aware of the consequences it will bring (crashes, constant updates) when downloading it and didn’t want to setup regular Firefox from scratch

[–] [email protected] 5 points 1 year ago

Thank you for answering is full sentences instead of on "nevermind, fixed it, bye"

[–] [email protected] 1 points 1 year ago (1 children)

When I changed it in about:config, About Firefox still showed update channel aurora. So I changed it in channel-prefs.js file, now there is no update channel mention in About Firefox.

[–] [email protected] 1 points 1 year ago (1 children)

I would wait and see if channel gets updated after next update

[–] [email protected] 1 points 1 year ago (1 children)

How's your browser doing? Mine doesn't want to update. It says download new version from website.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

Mine is still updating from aurora channel 😕 I’m on v118.0b2 now. Guess it didn’t really work