Repository navigation
ci: allow running the publish workflow manually - #684
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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
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.
The squash commit for #683 contained the literal skip-CI marker (it described the release commit format), so GitHub skipped every workflow for it and the first release-it release never ran.
This adds
workflow_dispatchtopublish.ymlso a release can be re-run by hand when that happens. Merging this PR is itself a normal push tomaster, so it triggers the release (2.11.5).The guard step still applies to manual runs: nothing is released unless there's a
feat/fix/perf/breaking commit since the last tag.Note for merging: check the squash commit message has no skip-CI marker in square brackets before confirming.
🤖 Generated with Claude Code