docs(release-trigger): explain what fires the release workflow - #32
Merged
Conversation
Add a "What triggers the workflow (and what doesn't)" section to docs/releasing.md. Covers the intended tag-push path, why the GitHub UI "Draft a new release" button clashes with the workflow's own Release-creation step, that merges never publish, and how workflow_dispatch behaves with dry_run. Motivated by a question about whether creating a GitHub Release triggers publishes — the answer is "yes but don't, push a tag instead." Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
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.
Summary
Adds a "What triggers the workflow (and what doesn't)" section to docs/releasing.md, sparked by a question about whether creating a GitHub Release via the UI publishes packages.
Covers:
v*tag → yes (intended path).main→ never publishes.workflow_dispatch→ yes;dry_run: trueis the smoke-test path.Also notes that flipping to
on: release: types: [published]is an option if you'd rather drive releases from the UI.Test plan