fix: pin GitHub Actions to commit SHAs in publication-builder - #3187
Merged
gtrivedi88 merged 1 commit intoSep 2, 2026
Merged
Conversation
Mitigate supply chain attacks (CVE-2025-30066) by pinning every action reference to an immutable commit SHA. This workflow uses CHE_BOT_GITHUB_TOKEN, making it a higher-risk target. Ref: https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/273 Co-authored-by: Cursor <cursoragent@cursor.com>
|
⚡️ Deploying pull request preview... |
|
Click here to review and test in web IDE: |
-525C86?logo=eclipse-che&labelColor=red){kind=icon}
ibuziuk
approved these changes
Sep 2, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Pin the 3 GitHub Actions references in
publication-builder.yamlto immutable commit SHAs. This is a companion to #3186 (which covers themainbranch).This workflow is higher-risk because it uses
CHE_BOT_GITHUB_TOKEN(a long-lived bot token with repo write access).actions/checkout@v3# v4actions/cache@v3# v4peaceiris/actions-gh-pages@v3# v3Ref: https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/273
Test plan
Made with Cursor