tools: fix failing release-proposal linter for LTS transitions #60465
+7
−3
Conversation
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
|
Review requested:
|
richardlau
approved these changes
Oct 29, 2025
aduh95
added
the
author ready
richardlau
reviewed
Oct 29, 2025
marco-ippolito
approved these changes
Oct 29, 2025
aduh95
added
the
commit-queue
cjihrig
approved these changes
Oct 29, 2025
nodejs-github-bot
removed
the
commit-queue
|
Landed in fdcf4d9 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
In #60414, the release-proposal linter was failing because it was expecting to see the commits from the previous release.