scripts: standardize release tagging scripts - #7
Merged
Conversation
Unify publish_release_tag.sh across PyDevices repos to a single interface: optional explicit VERSION arg, else auto (next_release_version.sh = highest vX.Y.Z tag + 1 patch, ignoring pre-release tags). Same script names and behavior everywhere for easier maintenance. Co-authored-by: Brad Barnett <bdbarnett@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
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.
Standardizes the release tagging scripts to a single shared interface across all PyDevices repos (same names + behavior, easier to maintain).
scripts/publish_release_tag.sh [VERSION] [--push] [--dry-run]— now supports auto version (in addition to the explicit arg it already took); creates an annotated tag;--pushtriggers this repo's publish workflow.scripts/next_release_version.sh(new) — highestvX.Y.Ztag + 1 patch (ignores non-semver/pre-release tags); falls back tosetup.py/pyproject/VERSION/0.0.1when no tags.Verified:
./scripts/next_release_version.sh→0.0.5.