Repository navigation
ci(release): create the marketplace release tag with the App token - #711
Conversation
Only the organization's release Apps may create v* tags. GitHub refuses the built-in GitHub Actions integration as a bypass actor in an organization ruleset, so the agent-plugins-only ruleset that would have let the workflow token create the tag cannot exist. Create the tag with the repository's GitHub App instead, which the organization-wide ruleset already allows. No workflow here runs on tags or releases, so the App-created release starts nothing new. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai review |
Action performed
|
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
GitHub refuses the built-in GitHub Actions integration as a bypass actor in an organization ruleset (HTTP 422), so the agent-plugins-only creation ruleset from #930 was never created and agent-plugins stayed outside the creation restriction. agent-plugins now creates its release tag with botantler-1 (devantler-tech/agent-plugins#711), which the organization-wide ruleset already allows. Drop the exclusion and the unused ruleset, so one ruleset covers every repository. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
What
The
releasejob inrelease-please.yamlnow creates thevX.Y.Ztag and the GitHub release with the repository's GitHub App token (the organizationAPP_CLIENT_IDApp, which already opens the release PR) instead of the workflow token. The job's ownGITHUB_TOKENdrops to no permissions; the App token carriescontents: writeandpull-requests: write, the same two the job needed before.docs/marketplace-releases.mdnow says the App creates the tag.Why
devantler-tech/.github#930 restricts
v*tag creation to the organization's release Apps. agent-plugins was meant to keep the workflow token through its own organization ruleset with the GitHub Actions integration as the bypass actor, but GitHub refuses that actor in an organization ruleset (HTTP 422 when the ruleset is created), so that ruleset never existed. Creating the tag with the App, which the organization-wide ruleset already allows, is the end state that ruleset's own notes planned. Once this is onmain, a.githubfollow-up drops the agent-plugins exclusion and the unused ruleset.Effect
releaseevents, so nothing new starts.Validation
actionlint .github/workflows/release-please.yaml: no findings.zizmor --offline .github/workflows/release-please.yaml: no findings.Part of devantler-tech/.github#924.
🤖 Generated with Claude Code