docs: channel branches need environment deployment-branch allowances#106
Merged
Conversation
theoephraim
added a commit
that referenced
this pull request
Jun 13, 2026
Promotes the `next` prerelease channel to stable. This merge carries the cycle's accumulated bump files (in `.bumpy/next/`) into main — versions never diverged, so the diff is the feature work plus file moves. On merge, main's release workflow will open the ordinary stable version PR: `@varlock/bumpy` → **1.14.0**, with a consolidated changelog entry built from the cycle's bump files. The `@next` dist-tag has shipped `1.14.0-rc.0` and `1.14.0-rc.1` through this cycle. What's in the cycle: - **Prerelease channels** ([#104](#104)) — branch-based prerelease lines; versions derived at publish time, never committed. - **Deterministic channel release PR titles** ([#107](#107)) — wildcard `rc.x` counters in PR titles/bodies/commits so they can't drift from the registry; package count for multi-package cycles. Validated live on [#109](#109). - **Docs** ([#106](#106)) — environment deployment-branch allowances for channel branches with trusted publishing. --------- Co-authored-by: bumpy 🐸 <bumpy.bot@varlock.dev> Co-authored-by: bumpy-bot <276066384+bumpy-bot@users.noreply.github.com>
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.
When the publish job runs in a GitHub Environment with deployment branch restrictions (our recommended hardening restricts it to
main), prerelease channel branches can't enter the environment — with trusted publishing this means OIDC token requests are rejected and channel publishes fail.Adds reminders in both places users would hit this:
main" hardening bullet now notes channel branches must be added to the allowed list.