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

actions: Only pin the checkout action to a major version #331

Conversation

primeos-work
Copy link
Member

@primeos-work primeos-work commented Jan 4, 2024

The actions/checkout action is from a trusted source (official GitHub Actions), this is in line with the documentation/examples 0, and it enables us to automatically get useful updates 1:

If the action publishes major version tags, you should expect to
receive critical fixes and security patches while still retaining compatibility. Note that this behavior is at the discretion of the action's author.

This especially makes sense since we already use this approach for all other included actions [2] (so it's finally consistent as well!). (Note: For 3rd-party actions it could make sense to use a more secure approach (commit SHA) but we don't need any secrets for CI and the sources should be trustable so our current approach should be fine.)

[2]: See git grep -hoE '[^ ]+@[^ ]+' -- .github/workflows/ | sort -u


See https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions regarding security considerations.

The `actions/checkout` action is from a trusted source (official GitHub
Actions), this is in line with the documentation/examples [0], and it
enables us to automatically get useful updates [1]:
> If the action publishes major version tags, you should expect to
receive critical fixes and security patches while still retaining
compatibility. Note that this behavior is at the discretion of the
action's author.

This especially makes sense since we already use this approach for all
other included actions [2] (so it's finally consistent as well!).
(Note: For 3rd-party actions it could make sense to use a more secure
approach (commit SHA) but we don't need any secrets for CI and the
sources should be trustable so our current approach should be fine.)

[0]: https://github.com/actions/checkout/blob/v4/README.md
[1]: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsuses
[2]: See `git grep -hoE '[^ ]+@[^ ]+' -- .github/workflows/ | sort -u`

Signed-off-by: Michael Weiss <michael.weiss@eviden.com>
@primeos-work primeos-work added this pull request to the merge queue Jan 4, 2024
Merged via the queue into science-computing:master with commit f46fd91 Jan 4, 2024
13 checks passed
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.

1 participant