Skip to content

ci(release): create release tags with a deploy key - #54

Merged
jo16oh merged 1 commit into
mainfrom
ci/release-tag-deploy-key
Sep 24, 2026
Merged

jo16oh merged 1 commit into
mainfrom
ci/release-tag-deploy-key

Conversation

@jo16oh

@jo16oh jo16oh commented Sep 24, 2026 •

Copy link
Copy Markdown
Owner

The next release fails at "Create tag". The tags ruleset blocks tag creation for GITHUB_TOKEN, and adding GitHub Actions as a bypass actor fails on a personal repository with:

422 Actor GitHub Actions integration must be part of the ruleset source or owner organization
  • Push the tag over SSH with a deploy key, the ruleset's only bypass actor
  • Keep the key as RELEASE_TAG_KEY in the release environment, limited to main
  • Load the key into an ssh-agent that ends with the step, so it is never written to disk
  • Run the whole release job in that environment. If npm's trusted publisher names an environment, it must be release

The deploy key, the environment and the ruleset bypass are already set up. The SSH push has not run yet; the first release tests it.

- Only deploy keys bypass the `tags` ruleset, because a personal repository cannot list GitHub Actions as a bypass actor
- Key in the `release` environment (main only), loaded into an ssh-agent for the tag step alone
@jo16oh
jo16oh force-pushed the ci/release-tag-deploy-key branch from 4b13b22 to 4f01a51 Compare September 24, 2026 11:56
@jo16oh
jo16oh merged commit e4e95bb into main Sep 24, 2026
2 checks passed
@jo16oh
jo16oh deleted the ci/release-tag-deploy-key branch September 24, 2026 14:36
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.

1 participant