Drop .dev0 suffix: bump to 0.1.0 for first stable PyPI release#7
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
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
Two-line version-string change so DCEBE actually ships a stable PyPI release.
Why
The `v0.1.0` git tag triggered a release run that uploaded `dcebe-0.1.0.dev0` to PyPI. `pip install dcebe` skips dev versions by default, so users see "No matching distribution found". This PR drops the `.dev0` suffix so the next tag publishes `dcebe 0.1.0` proper.
Required follow-up after merge
The existing `v0.1.0` tag points at the old `0.1.0.dev0` commit. After merging this PR, force-replace the tag:
```sh
git tag -d v0.1.0
git push origin --delete v0.1.0
git checkout master && git pull
git tag -a v0.1.0 -m "First stable PyPI release"
git push origin v0.1.0
```
This is safe because no `dcebe 0.1.0` (proper) artifact exists on PyPI yet — only the orphan `0.1.0.dev0`. The new tag will trigger `release.yml` which uploads `dcebe-0.1.0` alongside the dev0 (PEP 440 ordering: `0.1.0.dev0 < 0.1.0`, so `pip install dcebe` resolves to the new one).
Test plan