Skip to content
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

GHA: Update/fix actions #2592

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

GHA: Update/fix actions #2592

wants to merge 4 commits into from

Conversation

dgw
Copy link
Member

@dgw dgw commented Feb 14, 2024

Both actions/checkout and actions/setup-python were using deprecated Node runtimes and generating warnings in our CI logs. Oh, and they'd also eventually stop working entirely when the deprecated runtime is removed. That's probably the best reason to update them.

I also discovered that there is no v1 tag for pypa/gh-action-pypi-publish, so our existing pypi.yml workflow from #2328 wouldn't ever work. Because tags can be easily changed if a malicious someone gains access to the action's repository, the release action is pinned to a specific, verified, commit's SHA.

Checklist

  • I have read CONTRIBUTING.md
  • I can and do license this contribution under the EFLv2
  • No issues are reported by make qa (runs make lint and make test)
  • I have tested the functionality of the things this change touches
    • This will be handled for the ci.yml workflow by PR checks, and if the checkout & setup-python actions work there we can assume the same new versions will also work in the pypi.yml workflow.
    • I can't really test the pypi.yml workflow but that's no change (it was already untested), and we'll have a chance to test it for real soon enough.

Both of these actions were using deprecated Node runtimes and generating
warnings in our CI logs.

Oh, and they'd also eventually stop working entirely when the deprecated
runtime is removed. That's probably the best reason to update them.
See earlier commit updating CI workflow deps for commentary.
This action doesn't provide a rolling 'v1' tag due to security concerns.
The same security concerns exist when using a tag, so we use a specific
(signed) commit's SHA.
@dgw dgw added Build Housekeeping Code cleanup, removal of deprecated stuff, etc. labels Feb 14, 2024
@dgw dgw requested a review from a team February 14, 2024 21:47
@dgw
Copy link
Member Author

dgw commented Feb 25, 2024

Noticed that https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/ had slipped by. Better to catch it now than having the analysis suddenly break in December.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Build Housekeeping Code cleanup, removal of deprecated stuff, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant