docs: update version support page with LTS support phases - #2476
Open
bjohansebas wants to merge 2 commits into
Open
docs: update version support page with LTS support phases#2476bjohansebas wants to merge 2 commits into
bjohansebas wants to merge 2 commits into
Conversation
Add a support phase column to the version table, marking v5 as ACTIVE and v4 as MAINTENANCE with its earliest EOL date, and document the CURRENT/ACTIVE/MAINTENANCE phases introduced with the Express 5.1 LTS strategy. Also note that packages under the expressjs, jshttp, and pillarjs orgs are supported at least as long as the release lines that depend on them.
✅ Deploy Preview for expressjscom-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
UlisesGascon
requested changes
Aug 3, 2026
UlisesGascon
left a comment
UlisesGascon
left a comment
Member
There was a problem hiding this comment.
I think that probably makes sense to land this with the final date for 4.x
| | Major Version | Minimum Node.js Version | Support Start Date | Support Phase | Support End Date | | ||
| | -------------------------------------------------------------- | ----------------------- | ------------------ | ------------- | ------------------------------- | | ||
| | [**v5.x**](/5x/api) | 18 | September 2024 | `ACTIVE` | **not yet determined** | | ||
| | [**v4.x**](/4x/api) | 0.10.0 | April 2014 | `MAINTENANCE` | **no sooner than October 2026** | |
Member
There was a problem hiding this comment.
Suggested change
| | [**v4.x**](/4x/api) | 0.10.0 | April 2014 | `MAINTENANCE` | **no sooner than October 2026** | | |
| | [**v4.x**](/4x/api) | 0.10.0 | April 2014 | `MAINTENANCE` | December 2026 | |
Member
There was a problem hiding this comment.
Ending support for 4.x in 2026 might work fine... do we prefer April 2027? or another date?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a support phase column to the version table, marking v5 as ACTIVE and v4 as MAINTENANCE with its earliest EOL date, and document the CURRENT/ACTIVE/MAINTENANCE phases introduced with the Express 5.1 LTS strategy. Also note that packages under the expressjs, jshttp, and pillarjs orgs are supported at least as long as the release lines that depend on them.
I guess it's not too bad to fix this information a year later.
Please don't merge this without TC approval. 🙂
ref: https://github.com/expressjs/discussions/blob/master/docs/adr/352-lts-strategy.md