fix: make dev-publish workflow runnable and main-only - #21
Merged
Merged
Conversation
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.
The first version of dev-publish.yml was rejected by the Actions runner (0 jobs, failed runs) on its initial merges; this PR replaces it with a minimal structure matching the working publish.yml, moves the release-prep skip into scripts/dev_version.py (HEAD_MESSAGE env + git fallback), adds a ref guard so only pushes to main publish, and a dry_run input for validation.
Validated via workflow_dispatch on the branch (dry_run): version derivation, build, and skip-publish all succeeded. On merge, the push to main will publish the first automatic dev pre-release (0.2.1.devN) to PyPI.