fix: add contents:write permission to core release workflow - #2707
Open
cs-raj wants to merge 1 commit into
Open
Conversation
gh release create requires contents:write on the GITHUB_TOKEN. Add it at the job level in the reusable workflow and at the top level in the pipeline caller so it propagates correctly. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
✅ BUILD PASSED - All security checks passed |
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
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.
Root Cause
gh release createrequirescontents: writeon theGITHUB_TOKEN. The default token permission iscontents: read, causing the 403:Fix
release-production-core.yml— addedpermissions: contents: writeat the job level (this is the reusable workflow that actually runsgh release create)release-production-pipeline.yml— addedpermissions: contents: writeat the workflow level so it propagates into the reusable workflow call viaworkflow_callFiles Changed
.github/workflows/release-production-core.yml.github/workflows/release-production-pipeline.yml