chore(release): set version to 0.3.0-dev (Dev Release 3)#32
Merged
Conversation
Aligns the code version with the dev-release tag scheme (v0.3.0-dev, Dev Release 3). Parses cleanly via packaging (normalizes to 0.3.0.dev0) so the in-app updater's version comparison keeps working.
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.
Bumps
src/glider/_version.pyto0.3.0-dev, aligning the code version with the dev-release tag scheme (v0.3.0-dev) for Dev Release 3.0.3.0-devis valid PEP 440 (normalizes to0.3.0.dev0), so the in-app updater'spackaging-based version comparison keeps working.GLIDER-0.3.0-dev-arm64.dmg.Note: the CHANGELOG's latest heading is still
[1.1.0], which is higher than0.3.0-dev— the changelog and the dev-tag scheme have diverged. Left as-is; reconcile separately if desired.