-
Notifications
You must be signed in to change notification settings - Fork 531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
changelog v127, v128, v129, v130, v131, v132 #1887
Comments
Why did we launch v128 when Firefox is already on v129? 🤔 |
for ESR users - edit: and we don't have 129 diffs yet |
On amiunique.org shows me UTC=0 but on panoptic is Reykjavik |
Why |
Yes. Edit: bugzilla for you https://bugzilla.mozilla.org/show_bug.cgi?id=1803234 |
FYI: bounce tracking added to ETP Strict in FF133+ |
This is just a heads up that bug 1917177 (or |
1917177 - indeed, which is why you should always update :) This will also split TB users who don't update, on a passive FP level - FYI @morganava @PieroV - one day when TZP has it's own dedicated site and can report headers, this shit will just show up automagically |
🟩 v127/v128
FF127 release notes
FF127 for developers
FF127 security advisories
FF128 release notes
FF128 for developers
FF128 security advisories
CHANGELOG
⭐ Please do not use this issue to talk about RFP changes - use #1804
9999: DEPRECATED / REMOVED
STATS
🟩 v129
FF129 release notes
FF129 for developers
FF129 security advisories
no release - nothing to change - #1889
🟩 v130
FF130 release notes
FF130 for developers
FF130 security advisories
no release - one pref added currently/still at default - rolling over to next arkenfox version - #1890
🟩 v131
FF131 release notes
FF131 for developers
FF131 security advisories
no release - nothing to change - #1907
🟩 v132
FF132 release notes
FF132 for developers
FF132 security advisories
no release - one pref deprecated, one inactive pref removed - rolling over to next arkenfox version - #1911
The text was updated successfully, but these errors were encountered: