-
Notifications
You must be signed in to change notification settings - Fork 1
[Security] Pin GitHub Actions to a full-length commit SHA #102
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -33,7 +33,7 @@ jobs: | |
| crate: '${{ matrix.crate }}' | ||
|
|
||
| build: | ||
| uses: Datadog/action-prebuildify/.github/workflows/build.yml@main | ||
| uses: Datadog/action-prebuildify/.github/workflows/build.yml@d4e89247e6dd34f485c0f92c12f0cc739c2f8c92 # main | ||
| needs: build-test-wasm | ||
| with: | ||
| package-manager: 'yarn' | ||
|
|
@@ -57,6 +57,6 @@ jobs: | |
| uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0 | ||
| - run: yarn install | ||
| - name: Compute module size tree and report | ||
| uses: qard/heaviest-objects-in-the-universe@v1 | ||
| uses: qard/heaviest-objects-in-the-universe@1e02edbdda803a45537a808ede97866db47756d3 # v1.0.0 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The versions in Quards repo is messed up which is also why I think I left it out when I previously upgraded this action to use commit SHAs.
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good point, the reason why the tool expanded
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The reason why I left this one out when I updated all the other references to use the commit hash in a previous PR, was because its repository doesn't use semver git tags and several of the published versions to npm doesn't even have associated tags. So I think the best thing to do here is just hardcode the commit SHA like we do here. The
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sounds good! |
||
| with: | ||
| github-token: ${{ secrets.GITHUB_TOKEN }} | ||
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.
The description of this PR says:
but this seems to be an internal action? I suppose something choked on the different capitalization...
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 you're right, the code is case sensitive, I will update it to prevent this to happen again, thank you for flagging 🙇