Skip to content

Fix release workflow: Add permissions and use correct GitHub Actions token#19

Merged
cto-new[bot] merged 1 commit into
mainfrom
ci-fix-gh-release-403
Nov 4, 2025
Merged

Fix release workflow: Add permissions and use correct GitHub Actions token#19
cto-new[bot] merged 1 commit into
mainfrom
ci-fix-gh-release-403

Conversation

@cto-new

@cto-new cto-new Bot commented Nov 4, 2025

Copy link
Copy Markdown
Contributor

Summary

This PR fixes the release workflow in GitHub Actions, resolving 403 errors that prevented automated GitHub Releases when tags are pushed.

Details

  • Adds permissions: contents: write to the release job in the CI workflow
  • Replaces usage of secrets.GH_TOKEN with secrets.GITHUB_TOKEN (the built-in GitHub Actions token)
  • Ensures softprops/action-gh-release@v2 can publish releases successfully
  • No application/runtime changes; addresses CI/CD and deployment reliability

Warning: Task VM test is not passing, cto.new will perform much better if you fix the setup

Fixes 403 errors during the release process by updating the GitHub Actions workflow.
- Adds explicit `permissions: contents: write` to the `release` job
- Replaces custom `secrets.GH_TOKEN` with built-in `secrets.GITHUB_TOKEN`
- Ensures `softprops/action-gh-release@v2` can create releases as intended

These changes are required by recent GitHub security best practices and resolve blocked deployments when tagging releases.
@cto-new cto-new Bot merged commit 503fe06 into main Nov 4, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants