Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

nodejs_20: 20.11.1 -> 20.12.0 #299327

Merged
merged 1 commit into from
Mar 27, 2024
Merged

nodejs_20: 20.11.1 -> 20.12.0 #299327

merged 1 commit into from
Mar 27, 2024

Conversation

marsam
Copy link
Contributor

@marsam marsam commented Mar 26, 2024

Changelog: https://github.com/nodejs/node/releases/tag/v20.12.0

Description of changes

Things done

  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
    • sandbox = relaxed
    • sandbox = true
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
  • Fits CONTRIBUTING.md.

Add a 馃憤 reaction to pull requests you find important.

@marsam marsam changed the base branch from master to staging March 27, 2024 00:51
@marsam marsam merged commit 973d6ef into NixOS:staging Mar 27, 2024
28 of 30 checks passed
@marsam marsam deleted the update-nodejs_20 branch March 27, 2024 03:25
@bradzacher
Copy link

I notice this was merged into staging and not master.
What's the workflow for promoting this to master?

@jakubm-canva
Copy link

@marsam - is there a timeline to promote to master?

@marsam
Copy link
Contributor Author

marsam commented Apr 3, 2024

Hi, sorry for the delay

I notice this was merged into staging and not master.

yes, I usually send nodejs_20 to staging, because building it locally is resource intensive, and it may hurt contributors that use master branch. However, security releases always land in master first.

What's the workflow for promoting this to master?

Do you mean the staging workflow? I think it's documented in RFC 26 and CONTRIBUTING.md.

is there a timeline to promote to master?

The previous staging-next branch was merged a couple of days ago. So, I expect this to land in master during the week of April 15.

btw, is there anything in this version that could have been better if it landed in master first?

@jakubm-canva
Copy link

jakubm-canva commented Apr 4, 2024

Thanks for the update.

There is an important fix that makes the network connections not to fail: nodejs/node#51045
That's pretty much all in it.

@jakubm-canva
Copy link

@marsam - any updates on the merge to master?

@marsam
Copy link
Contributor Author

marsam commented Apr 19, 2024

it's already on master (staging-next PR #303527)

@vcunat
Copy link
Member

vcunat commented Apr 20, 2024

Generally you can use tools like https://nixpk.gs/pr-tracker.html?pr=299327

@bradzacher
Copy link

That would be great to have a bot auto-post that link for discoverability!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants