-
Notifications
You must be signed in to change notification settings - Fork 214
change to use pinned version for trusted actions #2222
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
ofek1weiss
merged 1 commit into
master
from
app-1011-pin-buildin-actions-to-version-instead-of-hash
Apr 28, 2026
+16
−32
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
🧩 Analysis chain
🏁 Script executed:
Repository: elementary-data/elementary
Length of output: 4394
🏁 Script executed:
Repository: elementary-data/elementary
Length of output: 104
🏁 Script executed:
cat -n .github/workflows/release.yml | head -200Repository: elementary-data/elementary
Length of output: 7254
Pin release workflow actions to immutable commit SHAs, not floating version tags.
Lines 48, 53, 105, 110, 121, 142, 147, 150, 153, 161, 169, and 186 use floating major version tags (e.g.,
@v6,@v4,@v7) instead of commit SHAs. In release workflows that publish to PyPI and GHCR, this creates non-reproducible and mutable execution behavior—the workflow can behave differently across different release runs if action maintainers update the tag. This weakens supply-chain integrity and auditability.Replace each action reference with its corresponding commit SHA (you can preserve the version as an inline comment for clarity):
actions/checkout@v6→de0fac2e4500dabe0009e67214ff5f5447ce83ddactions/setup-python@v6→a309ff8b426b58ec0e2a45f0f869d46889d02405actions/upload-artifact@v6→b7c566a772e6b6bfb58ed0dc250532a479d7789fdocker/setup-qemu-action@v4→ce360397dd3f832beb865e1373c09c0e9f86d70adocker/setup-buildx-action@v4→4d04d5d9486b7bd6fa91e7baf45bbb4f8b9deedddocker/login-action@v4→4907a6ddec9925e35a0a9e82d7399ccc52663121docker/metadata-action@v6→030e881283bb7a6894de51c315a6bfe6a94e05cfdocker/build-push-action@v7→bcafcacb16a39f128d818304e6c9c0c18556b85f🤖 Prompt for AI Agents
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.
since these are trusted vendors, we choose to trust their version tags
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.
@ofek1weiss, understood — using major version tags for trusted vendors likeactions/*anddocker/*is a reasonable tradeoff, and I'll respect that decision going forward.✏️ Learnings added