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>
Why
#930 restricted who may create release tags, with a separate rule for agent-plugins that let its release workflow's built-in token create the tag. GitHub does not accept that built-in identity as an exception in an organization rule, so the agent-plugins rule was never created and keeps failing to apply.
What
agent-plugins now creates its release tag with the organization's release App, like every other product. This removes the agent-plugins exception and its unused rule, so one rule covers every repository. The guard test now pins that single rule and rejects any exception coming back.
Part of #924
Deletion-Acknowledged: OrganizationRuleset.enterprise.github.m.upbound.io/restrict-agent-plugins-release-tag-creation
The removed rule never existed in GitHub (every create attempt was refused), so pruning it changes nothing in the live organization.
👉 After merge: the change takes effect with this repository's next release, when the platform applies it.
🤖 Generated with Claude Code