Skip to content

Conversation

@salmanmkc
Copy link

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.yml
actions/upload-artifact v4 v6 Release build.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
Member

@jan-wassenberg jan-wassenberg left a comment

Choose a reason for hiding this comment

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

Thanks!

@jan-wassenberg jan-wassenberg added copybara-import Trigger Copybara for merging pull requests and removed copybara-import Trigger Copybara for merging pull requests labels Dec 16, 2025
Copy link
Member

@jan-wassenberg jan-wassenberg left a comment

Choose a reason for hiding this comment

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

Oh, I see the target is main branch, we are only able to merge to the dev branch, would you please rebase the PR?

@salmanmkc
Copy link
Author

Oh, I see the target is main branch, we are only able to merge to the dev branch, would you please rebase the PR?

Ah sure

@salmanmkc salmanmkc changed the base branch from main to dev December 16, 2025 14:47
jan-wassenberg
jan-wassenberg previously approved these changes Dec 16, 2025
Copy link
Member

@jan-wassenberg jan-wassenberg left a comment

Choose a reason for hiding this comment

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

Thanks again :D

@jan-wassenberg jan-wassenberg added the copybara-import Trigger Copybara for merging pull requests label Dec 16, 2025
@salmanmkc
Copy link
Author

Thanks again :D

My pleasure, thanks for the quick review!

@salmanmkc salmanmkc changed the base branch from dev to main December 16, 2025 17:49
@salmanmkc salmanmkc changed the base branch from main to dev December 16, 2025 17:50
@salmanmkc salmanmkc dismissed jan-wassenberg’s stale review December 16, 2025 17:50

The base branch was changed.

@salmanmkc
Copy link
Author

salmanmkc commented Dec 16, 2025

@jan-wassenberg sorry I was just running checks on my PRs to see if they targetted the wrong branch, and it seems like it identified that the base branch in this repo was supposed to be main and then changed it, dimissing your review, I've changed it back to dev. Sorry about that.

Copy link
Member

@jan-wassenberg jan-wassenberg left a comment

Choose a reason for hiding this comment

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

No worries, stamped again :)

@jan-wassenberg jan-wassenberg added copybara-import Trigger Copybara for merging pull requests and removed copybara-import Trigger Copybara for merging pull requests labels Dec 17, 2025
@copybara-service copybara-service bot merged commit 11aa16a into google:dev Dec 19, 2025
8 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

copybara-import Trigger Copybara for merging pull requests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants