nodejs_latest: 25.9.0 -> 26.0.0-rc.1#511783
Merged
Merged
Conversation
Contributor
Author
|
@NixOS/nixpkgs-vet is it fine to ignore the CI failure here? |
Member
|
I think it’s fine, but will wait a bit longer for them to weigh in. |
winterqt
approved these changes
Apr 22, 2026
Contributor
Author
|
I'd like to merge this before the release freeze, if I don't hear any objections |
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.
Node.js 25.x will be EOL during 26.05 lifetime, so IMO it makes sense to switch to the 26 RC like we did back in #395431
Things done
passthru.tests.nixpkgs-reviewon this PR. See nixpkgs-review usage../result/bin/.