Add Firefox release automation script

[pepelsbey]

Description

It’s an automation script that helps to create Firefox release notes.

I created the Firefox 145 release notes PR using this script.

Motivation

To simplify release notes workflow.

Additional details

How it works, for example, with the newly released Firefox 145:

node scripts/content/release-firefox.js 145

What it does:

Takes the newly released version as a parameter (N), and:

• Removes active from N-1
• Updates N to Stable
  • Uncomments HTML, CSS, JavaScript “no notable changes” sections
  • Removes all other unused commented sections
• Updates N+1 to Beta
• Adds Nightly N+2 page

For release dates, it uses official JSON API — https://whattrainisitnow.com/api/firefox/calendar/future/

Related issues and pull requests

• Release Firefox 145 #41896

[bsmth]

I ran:

node helpers/release-firefox.js 146
# ...
	modified:   files/en-us/mozilla/firefox/releases/145/index.md
	modified:   files/en-us/mozilla/firefox/releases/146/index.md
	modified:   files/en-us/mozilla/firefox/releases/147/index.md
	new file:   files/en-us/mozilla/firefox/releases/148/index.md

• 145 LGTM
• 146 LGTM
• 147 LGTM
• 148 LGTM

Note that if you run for a past version, you will get:

🦊 Firefox Release Notes Updater

📋 Planned updates:
   Firefox 144 → Remove active status
   Firefox 145 → Stable
   Firefox 146 → Beta
   Firefox 147 → Nightly (new page)

📡 Fetching release dates...
⚠️  Warning: Could not find all release dates.
   Stable (145): NOT FOUND
   Beta (146): 2025-12-09
   Nightly (147): 2026-01-13

❌ Error: Missing required release dates. Cannot proceed.

So I presume in the current state, if you run this on or after the day of release, it will trip on that.

[bsmth]

Only thing to sort is where it lives, but once it's in a good home, this is good to merge, IMO. Do we want to couple this with a CODEOWNER change for convenience?

[Josh-Cena]

Any problem with just putting all scripts under scripts/?

[pepelsbey]

Any problem with just putting all scripts under scripts/?

That's what I initially thought. But it turned out we need to differentiate content helpers from scripts used for build and CI, as they have different levels of importance and need to be reviewed by the engineering team.

[Josh-Cena]

You can just add another entry in the CODEOWNERS file though. Earlier entries override later ones.

[bsmth]

You can just add another entry in the CODEOWNERS file though. Earlier entries override later ones.

If it's in ./scripts/content, for example, CODEOWNERS could look like:

# Scripts and Tests
/scripts @mdn/engineering
+/scripts/content @mdn/content-team
/tests   @mdn/engineering

[pepelsbey]

@bsmth Thanks! I implemented your suggestions:

• Moved script to the scripts/content subfolder.
• Changed CODEOWNERS.
• Split template into a Markdown file.

It looks ready for the upcoming release project :)

[bsmth]

Looking good, thanks. Tested again with:

node scripts/content/release-firefox.js 146

And works as expected 👍🏻

[pepelsbey]

Thanks everyone!