Skip to content

Conversation

@salmanmkc
Copy link
Contributor

Summary

Upgrade GitHub Actions to their latest versions to ensure compatibility with Node 24, as Node 20 will reach end-of-life in April 2026.

Changes

Action Old Version(s) New Version Release Files
actions/checkout v4 v6 Release build-test-images.yml, containerization-build-template.yml
actions/download-artifact v4 v7 Release containerization-build-template.yml
actions/upload-artifact v4 v6 Release containerization-build-template.yml

Context

Per GitHub's announcement, Node 20 is being deprecated and runners will begin using Node 24 by default starting March 4th, 2026.

Why this matters

  • Node 20 EOL: April 2026
  • Node 24 default: March 4th, 2026
  • Action: Update to latest action versions that support Node 24

Security Note

Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references.

Testing

These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging.

Copy link
Contributor

@jglogan jglogan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like we need a make fmt for some reason?

@katiewasnothere
Copy link
Contributor

@jglogan I think the CI just failed to install Hawkeye. Rerunning to see if that fixes it.

@salmanmkc
Copy link
Contributor Author

Yeah I don't think it's related to the change, hopefully CI passes this time.

@salmanmkc
Copy link
Contributor Author

Looks to be ok now 👍

@katiewasnothere
Copy link
Contributor

@salmanmkc Sorry should have checked earlier, can we use shas here as well?

@salmanmkc
Copy link
Contributor Author

salmanmkc commented Dec 16, 2025

No worries, and sure, will update it

Signed-off-by: Salman Muin Kayser Chishti <13schishti@gmail.com>
@salmanmkc
Copy link
Contributor Author

Sorry looks like shallow clone caused some issue and can't reopen this, so made a PR here with SHA pinning: #452

@salmanmkc
Copy link
Contributor Author

Pinned the SHA for the other PR too #451

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants