-
Notifications
You must be signed in to change notification settings - Fork 355
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
Bump Github Actions versions #913
Conversation
The master branch is no longer updated, it has since been migrated to be named main. Additionally, it is better to target a specific version to avoid breaking changes.
Now the version numbers are all consistent at v4. Previously, some were v3 and others were the unmaintained master branch (renamed to main).
Was previously as mix of v2 and v3. The only notable breaking changes were NodeJS version bump, which does not affect us.
Bump to v6. There are only two breaking changes, both of which don't affect anything else. The first changes the default email and name of the pull request created. The second cleans up some Git config, which is unused by us.
LGTM. I also looked at what's involved when updating shalzz/zola-deploy-action. The main concern is that it's updating Zola to v0.18.0 so we need to take a close look to this Zola version release changes before the bump |
Ok! I'll test that out, but it will definitely be in a separate PR. Thanks for the insight :) |
Co-authored-by: François <[email protected]>
Co-authored-by: François <[email protected]>
This PR increases the versions of actions used by CI. The specific actions being updated are split by commit. They are:
actions/checkout
to v4 (b9166c2)actions/upload-artifact
andactions/download-artifact
to v4 (c1cc6af)actions/cache
to v4 (bc782e7)peter-evans/create-pull-request
to v6 (459e9c9)A few versions were inconsistent across the project, so this fixes that too. I don't believe any of the breaking changes affect us, since most of the changes were bumping the NodeJS runtime to version 20. The other breaking changes are documented in the commit descriptions.
Many actions were targeting the
master
branch. Sincemaster
was renamed tomain
for all of those projects, runs were pulling what is equivalent of a random out-of-date commit from the repositories. I updated them to target actual releases, to avoid breaking changes.The only action I left outdated (that I'm aware of) is
shalzz/zola-deploy-action
since the release notes are more confusing and I didn't want to break anything. That may come in another PR.