Skip to content

Conversation

@torokati44
Copy link
Member

Referencing #18780, #20362, and #21950.

This will also necessitate updating the set of required checks for PRs, as usual.

@torokati44 torokati44 added A-web Area: Web & Extensions T-chore Type: Chore (like updating a dependency, it's gotta be done) labels Oct 17, 2025
@danielhjacobs
Copy link
Contributor

I don't mind this and it's how we've done updates in the past, but worth noting the odd number releases always have significantly shorter life-cycles than the even number releases. Node 22 will remain the maintenance release for over a year after Node 25 goes entirely out of maintenance: https://nodejs.org/en/about/previous-releases#release-schedule

@danielhjacobs
Copy link
Contributor

Still, the point of the tests is to catch breaking issues as early as possible, and the builds are still being done with even number releases, so it's probably fine. There's just the opposite argument to be had about testing for breakages with the maintenance release too. If CI resources were infinite, we'd ideally test both, but 🤷

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-web Area: Web & Extensions T-chore Type: Chore (like updating a dependency, it's gotta be done)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants