Skip to content

[CI] Update actions version and remove warnings #6546

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Nitish-bot
Copy link

Description
The current versioning was very old making us susceptible to security vulnerabilities and to using deprecated methods that currently throw warnings wherever and old version actions/checkout is used

This PR fixes #

Notes for Reviewers

  • Versioning should absolutely not refer to main or master branch since these can include breaking changes.
  • Versioning can either reference a fixed version (e.g., v4.2.2) or a flexible one (e.g., v4, which resolves to the latest v4.x.x). In this PR, I’ve opted to pin the version, but we can switch to a more flexible reference.

Signed commits

  • Yes, I signed my commits.

Signed-off-by: Nitish C <86357181+Nitish-bot@users.noreply.github.com>
@l5io
Copy link
Contributor

l5io commented Jun 13, 2025

🚀 Preview for commit 5891111 at: https://684bd9c4a8dcba4774e46afa--layer5.netlify.app

Signed-off-by: Nitish C <86357181+Nitish-bot@users.noreply.github.com>
@l5io
Copy link
Contributor

l5io commented Jun 13, 2025

🚀 Preview for commit df3e93f at: https://684c03e76c20e0007d3e57c2--layer5.netlify.app

@Nitish-bot
Copy link
Author

There is an argument to be made here, 'don't fix what ain't broke'. I differ in opinion and would say for the minimal amount of effort that this takes (which would be fixing any anomalies that show up as a result of these changes), it's well worth it to use newer versions.

My reasoning for not pointing to master or main branches of actions can be found here

Copy link

stale bot commented Jun 27, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the issue/stale Issue has not had any activity for an extended period of time label Jun 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci issue/stale Issue has not had any activity for an extended period of time
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants