-
Notifications
You must be signed in to change notification settings - Fork 20
Fix github action version by hash #273
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Pinning the
actions/setup-node
action to a specific commit hash (49933ea5288caeca8642d1e84afbd3f7d6820020
) is a great step for security!However, there appears to be a small discrepancy in the accompanying version comment. The comment
# v4.4.0
suggests this hash corresponds to version 4.4.0 ofactions/setup-node
. Upon checking, the commit49933ea5288caeca8642d1e84afbd3f7d6820020
is actually tagged asv4.0.0
in theactions/setup-node
repository (see actions/setup-node@v4.0.0).An accurate version comment is important for future maintainability and understanding. Could you please verify this and update the comment to
# v4.0.0
?Also, note that the
@v4
tag currently points to a newer version (e.g.,v4.0.2
). If your intention was to pin to the latest stablev4
release, you might consider using the hash for that version. However, pinning tov4.0.0
is perfectly valid; the main point here is to ensure the comment accurately reflects the pinned version.