-
Notifications
You must be signed in to change notification settings - Fork 93
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
Update Versions of GitHub Actions used #153
Conversation
@@ -16,10 +16,10 @@ jobs: | |||
|
|||
steps: | |||
- name: Checkout repository | |||
uses: actions/checkout@v2 | |||
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 is there a long hash here? Shouldn't it just be "v4"?
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.
v4
would also work; however, my understanding is that specifying the full version and SHA is preferable in general, because it is more difficult for a malicious hacker to compromise your code via a compromised version of the GitHub action. See https://docs.github.com/en/actions/security-for-github-actions/security-guides/security-hardening-for-github-actions#using-third-party-actions
Technically, I suppose that since this is an official GitHub action, it doesn't fall under the category of "third-party actions." I've just gotten into the habit of using the full SHA wherever I can. Then I let Dependabot, Renovate Bot, or similar tools suggest updates to my GH Actions when there are updates available.
Let me know if you prefer simply v4
or v4.2.2
, and I can update my PR accordingly.
Thanks!
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.
Let's just go with the version number, since it's an official GitHub action.
Would "v4" end up using 4.2.2, since it is the latest version of the "4.0" release? I'd like to keep it as simple as possible.
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.
Yes, v4
will use the latest v4 minor and patch version, so 4.2.2 currently.
OK, I will change it to just v4
. Thanks.
.github/workflows/maven.yml
Outdated
@@ -15,9 +15,9 @@ jobs: | |||
runs-on: ubuntu-latest | |||
|
|||
steps: | |||
- uses: actions/checkout@v2 | |||
- 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 is there a long hash here? Shouldn't it just be "v4"?
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.
See my response on the other instance of actions/checkout
Thanks for the pull request. Please see my comments. |
Merged, thanks! 👍 |
Uh oh, there's an error. Any chance you could look at this? https://github.com/mangstadt/ez-vcard/actions/runs/12486445652/job/34846521443 |
@mangstadt I took a look at the above error. #154 should fix it. Thanks! |
Hi there,
Thanks for the neat library! I wonder if you would be interested in some contributions to the project. Starting with a Pull Request to update the GitHub Actions to the latest versions.