Release 0.10.2a1 - #47
Closed
github-actions[bot] wants to merge 4 commits into
Closed
Conversation
…rdcoded pyproject value (#46) pyproject.toml pinned `version = "0.1.1a1"` under the hatchling backend, so every build shipped that exact string no matter how far version.py had been bumped by the release automation. Every dev-merge alpha publish since April has failed on PyPI with 400 File already exists because the wheel/sdist always claimed 0.1.1a1. Switch to the setuptools backend with dynamic version sourced from nebulento.version.__version__, matching the working palavreado/jurebes/linha-fina setup, so alpha publishes track the real bumped version again.
Closing: the change this addresses is included in release 0.10.3a1. |
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
2 participants
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.
Human review requested!