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
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
Bump the two third-party actions to their Node 24-compatible major versions:
Why
GitHub runners emit a deprecation warning on every run because both actions currently ship Node.js 20 binaries. Node 20 will be forced off on June 2, 2026 and removed from runners on September 16, 2026. Both actions have v5 releases that use Node 24 and clear the warnings.
Side-benefit
Opening this PR is also the first real exercise of the new preview-deploy flow. When this PR opens it should spin up `ci-bump-actions-v5.lef.fyi`. When it closes, the cleanup job should tear the bucket and CNAME back down. That's the whole contract the previous PR established, tested on itself.
Test plan