fix: replace update-flake-lock to drop Node.js 20 sub-actions#3
Merged
Conversation
DeterminateSystems/update-flake-lock pulls in four sub-actions still on the Node.js 20 runtime, which GitHub forces to Node.js 24 on 2026-06-16 and removes entirely on 2026-09-16. Its latest release (v28) still pins all four, and the two leaf actions doing PR-body templating have no Node.js 24 release at all, so bumping the dependency cannot fix it. Reimplement the step inline: `nix flake update --commit-lock-file` (pure Nix, no Node) produces the lock change and its per-input changelog, which becomes the PR body; peter-evans/create-pull-request@v8 (Node.js 24) opens the PR. Only one Node action remains in the chain and it runs on Node.js 24. Also add pr-title and pr-branch inputs (defaults preserve the previous title and branch name) so the PR title / commit summary and head branch are configurable.
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.
What
Replace the
DeterminateSystems/update-flake-lock@v28step inupdate-flake/action.ymlwith an inline implementation:nix flake update --commit-lock-file(pure Nix, no Node) +peter-evans/create-pull-request@v8(Node.js 24).Why
update-flake-lockpulls in four sub-actions still on the Node.js 20runtime (
write-file-action,read-file-action,handlebars-action,create-pull-request@v7). GitHub forces these to Node.js 24 on 2026-06-16and removes the Node.js 20 runtime on 2026-09-16.
The latest release (v28) still pins all four, and the two leaf actions doing
PR-body templating have no Node.js 24 release at all, so bumping the
dependency cannot fix it. Reimplementing inline leaves exactly one Node action
in the chain, on Node.js 24.
Notes
--commit-lock-filechangelog becomes the PR body (replacing thetemplating chain). Behavior, inputs and outputs are preserved.
pr-title/pr-branchinputs; defaults preserve the previous titleand branch name.
update-flake/. The realacceptance test is a consumer run showing no "Node.js 20 actions are
deprecated" annotation.