ci: gate publish behind the release environment - #6
Merged
Conversation
Merging a version bump auto-tags via the tag job, and the tag previously fired release.yml straight through to npm, GHCR, and a GitHub Release with no human in the loop. Point both release jobs at the `release` environment, which has required reviewers, so a tagged build stages and waits for approval instead of shipping itself. One approval unblocks both jobs in the run. CI already runs type-check and the test suite, so no change is needed there.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prep for a second contributor working across the MCP repos. Companion to ttpears/bookstack-mcp#17.
What this changes
Today, merging a PR that bumps
package.jsonversion makes thetagjob inci.ymlpush av*tag, which firesrelease.yml, which publishes to npm (with provenance), pushes GHCR images, and cuts a GitHub Release — with no human approval anywhere in the chain.Both jobs in
release.ymlnow target thereleaseenvironment, which is configured with required reviewers. A tagged build now stages and waits for approval. One approval unblocks both jobs in the run.Not changed
ci.ymlalready runsnpm run type-checkandnpm test, so no test-gate change was needed here (unlike bookstack-mcp, whose CI ran build only). Merging and tagging remain unrestricted — only the publish waits. PR preview images (docker-preview) are unaffected.