Repository navigation
docs(changes): move the #453 entry under 1.11.1 - #455
Merged
Merged
Conversation
The fix ships in 1.11.1, cut from the 1.11.0 tag on chore/release-1.11.1, so its entry leaves the unreleased section and gets its own 1.11.1 section, as on the release branch.
ekalinin
added a commit
to jihtsan/nodeenv
that referenced
this pull request
Oct 29, 2026
The integration, git-bash and with-npm-windows jobs failed on 6d6b79b because master did not have the ekalinin#453 fix yet: latest resolved to 27.0.0-alpha.0.0.0 and crashed in parse_version. Master now has it (ekalinin#454) and keeps the ekalinin#453 entry in its 1.11.1 section (ekalinin#455), so the merge has no conflicts.
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
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.
Follow-up to #454.
The #453 fix ships in 1.11.1, which is cut from the 1.11.0 tag on
chore/release-1.11.1so that it keeps 1.11.0's Python support. On master itsCHANGESentry still sits underVersion [unreleased], so 1.12.0 would list it again.This moves the entry into its own
Version 1.11.1section between[unreleased]and1.11.0. The section is the same text as onchore/release-1.11.1. README.rst plusCHANGESstill render withreadme_renderer.