FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

fix: add contents:write permission to core release workflow by cs-raj · Pull Request #2707 · contentstack/cli · GitHub

/ cli Public

fix: add contents:write permission to core release workflow - #2707

Open
cs-raj wants to merge 1 commit into
developmentfrom
fix/DX-10156-release-workflow-permissions
ConversationCommits (1)ChecksFiles changed
Open

fix: add contents:write permission to core release workflow#2707
cs-raj wants to merge 1 commit into
developmentfrom
fix/DX-10156-release-workflow-permissions

Conversation

cs-raj commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Root Cause

gh release create requires contents: write on the GITHUB_TOKEN. The default token permission is contents: read, causing the 403:

HTTP 403: Resource not accessible by integration
(https://api.github.com/repos/contentstack/cli/releases)

Fix

  • release-production-core.yml — added permissions: contents: write at the job level (this is the reusable workflow that actually runs gh release create)
  • release-production-pipeline.yml — added permissions: contents: write at the workflow level so it propagates into the reusable workflow call via workflow_call

Files Changed

  • .github/workflows/release-production-core.yml
  • .github/workflows/release-production-pipeline.yml

fix: add contents:write permission to core release workflow
4f84ba7 
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>
cs-raj requested a review from a team as a code owner August 12, 2026 13:25

snyk-io Bot commented Aug 12, 2026 •
edited
Loading

Copy link
Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues
✅ Licenses 0 0 0 0 0 issues
✅ Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

github-actions Bot commented Aug 12, 2026

Copy link
Copy Markdown

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 0 25 ✅ Passed
🟡 Medium Severity 0 2 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

ℹ️ 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:

  • Critical without fixes: 0
  • High without fixes: 0
  • Medium without fixes: 2
  • Low without fixes: 0

✅ 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
Show hidden characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

Back | FazBrowse Home | New Git URL