Uh oh!
There was an error while loading. Please reload this page.
fix: properly tag maintenance and flag versions correctly - #6586
Merged
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Contributor
Lighthouse Results
|
MemberAuthor
cc @nodejs/nodejs-website @nodejs/web-infra as this solves a (imo) a critical bug as we're misleading at the moment people to non-LTS versions as "LTS" Requesting Fast-Track |
Contributor
Unit Test Coverage Report
Unit Test Report
|
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 freeto 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.
Description
This PR fixes an issue of a maintenance version being flagged as "Maintenance LTS" and we not rendering correctly maintenance versions.
Validation
On the preview branch, LTS version should again be marked as v20
Related Issues
Closes#6584