chore: use PEP 440 .dev0 versions on main after releases#2032
Merged
mnriem merged 2 commits intogithub:mainfrom Mar 31, 2026
Merged
chore: use PEP 440 .dev0 versions on main after releases#2032mnriem merged 2 commits intogithub:mainfrom
mnriem merged 2 commits intogithub:mainfrom
Conversation
- Release-trigger workflow now adds a dev bump commit (X.Y.(Z+1).dev0) on the release branch after tagging, so main gets the dev version when the PR merges. The tag still points at the release commit. - Set current pyproject.toml to 0.4.4.dev0. - Replace broken release workflow badge with shields.io release badge.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the post-release versioning flow so main carries a PEP 440 development version (.dev0) after a release, avoiding confusion for users installing directly from main.
Changes:
- Bumps
pyproject.tomlonmainto0.4.4.dev0. - Enhances the release-trigger workflow to add a second commit on the release branch that bumps to
X.Y.(Z+1).dev0before opening the PR. - Replaces the README release workflow badge with a shields.io “latest release” badge.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| README.md | Swaps the release workflow badge for a latest-release badge. |
| pyproject.toml | Sets the project version to 0.4.4.dev0 on main. |
| .github/workflows/release-trigger.yml | Adds an automated “bump to next dev version” commit and updates PR title/body/summary accordingly. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
After a release,
mainshowed the same version as the published release (e.g.0.4.3), which confused users installing frommainviauv— they couldn't tell they had a development build.Changes
pyproject.tomltoX.Y.(Z+1).dev0before the PR is opened. The git tag still points at the release commit. PR title and summary updated to reflect the dev version.0.4.4.dev0somainis immediately correct.Result
uv tool install specify-cli --from git+https://github.com/github/spec-kit.git→0.4.4.dev0(clearly a dev build)uv tool install specify-cli --from git+https://github.com/github/spec-kit.git@v0.4.3→0.4.3(stable release)