chore(ci): bump actions to latest majors (Node 24 LTS)#26
Merged
Conversation
GitHub Actions will force the Node.js 24 runtime as the default on
2026-06-02 and remove Node.js 20 on 2026-09-16. The smoke runs of
publish-flex-image both surfaced deprecation warnings for the previous
versions. Node.js 24 has been the active LTS since October 2025, so
this bumps to majors that declare `using: node24` in action.yml.
Bumps:
actions/checkout v5 → v6
aws-actions/configure-aws-credentials v4 → v6
docker/setup-buildx-action v3 → v4
docker/build-push-action v5 → v7
aws-actions/amazon-ecr-login stays at v2 (v2.1.5 already on node24)
Breaking-change review:
- configure-aws-credentials v5 cleaned up boolean-input handling; we
pass only strings (role-to-assume, aws-region), unaffected.
- configure-aws-credentials v6 is a Node 24 migration only.
- build-push-action v6 enables build summaries by default (we accept
this side effect; opt-out via DOCKER_BUILD_SUMMARY=false if needed).
- build-push-action v7 is a Node 24 migration plus removal of deprecated
envs we don't use (DOCKER_BUILD_NO_SUMMARY, DOCKER_BUILD_EXPORT_RETENTION_DAYS).
- actions/checkout v6, docker/setup-buildx-action v4: Node 24 only.
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
1 participant
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.
Summary
Bumps the GitHub Actions referenced by
publish-flex-image.ymlandupstream-sync.ymlto their latest majors. All bumped actions now declareusing: node24in theiraction.yml, matching the current Node.js Active LTS (since Oct 2025).Why now
GitHub will force Node.js 24 as the default Actions runtime on 2026-06-02 and remove Node.js 20 on 2026-09-16. The smoke runs of
publish-flex-imageboth surfaced deprecation warnings on the prior versions.Bumps
actions/checkoutaws-actions/configure-aws-credentialsdocker/setup-buildx-actiondocker/build-push-actionaws-actions/amazon-ecr-loginBreaking-change review (two-major jumps)
aws-actions/configure-aws-credentialsv4 → v6role-to-assume,aws-region), so unaffected.docker/build-push-actionv5 → v7DOCKER_BUILD_SUMMARY=falseenv if undesired. We accept this — summaries are useful artifacts.DOCKER_BUILD_NO_SUMMARY,DOCKER_BUILD_EXPORT_RETENTION_DAYS) we don't use.Test plan
The publish workflow has a self-contained smoke test that exercises every action:
publish-flex-image.ymlwith a throwaway tag against dev:upstream-sync.yml— first scheduled run (next 09:00 UTC) or a manual dispatch with no inputs will exerciseactions/checkout@v6. Expect: "Up to date" notice (flex is on v0.9.5).Files changed
.github/workflows/publish-flex-image.yml.github/workflows/upstream-sync.yml