-
Notifications
You must be signed in to change notification settings - Fork 2
GitHub Actions: Pin versions for actions #26
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
Conversation
@@ -13,10 +13,10 @@ jobs: | |||
|
|||
steps: | |||
- name: Check out the repository | |||
uses: actions/checkout@v4 | |||
uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not directly pin to the corresponding tag?
(I understand the security concern, and am just suggesting the changes to avoid you waste time on rewriting the code... but if you prefer to keep it as-is that's also fine with me. The comment helps to understand what version we are dealing with, so the only con is maintenance but we can deal with that!)
uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2 | |
uses: actions/[email protected] |
|
||
- name: Install the latest version of uv and set the python version to 3.13 | ||
uses: astral-sh/setup-uv@v6 | ||
uses: astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc # v6.4.3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
uses: astral-sh/setup-uv@e92bafb6253dcd438e0484186d7669ea7a8ca1cc # v6.4.3 | |
uses: astral-sh/[email protected] |
@@ -14,12 +14,12 @@ jobs: | |||
runs-on: ubuntu-latest | |||
steps: | |||
- name: Check out the repository | |||
uses: actions/checkout@v4 | |||
uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2 | |
uses: actions/[email protected] |
with: | ||
fetch-depth: 0 | ||
|
||
- name: Set up Python | ||
uses: actions/setup-python@v5 | ||
uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # v5.6.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # v5.6.0 | |
uses: actions/[email protected] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you Peter! I am in favor of pinning these, even if I think the commit hash might be a bit overkill... But you added the corresponding tags as comments, and I think that is close enough to directly pinning to tags while being more secure.
No description provided.