chore: bump version to 0.6.0rc1#561
Merged
Merged
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The GAlgebra version pattern (-dev) didn't cover release candidates like 0.6.0rc1, causing nbval output mismatch failures in notebooks. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #561 +/- ##
=======================================
Coverage 73.46% 73.46%
=======================================
Files 22 22
Lines 4459 4459
=======================================
Hits 3276 3276
Misses 1183 1183 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…mpatible) releases extension uses semantic_version which rejects '0.6.0rc1' (PEP 440 format, not semver). The release marker will be added as ':release:`0.6.0`' for the final release. The _version.py bump to 0.6.0rc1 controls PyPI. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
utiberious
pushed a commit
to utiberious/galgebra
that referenced
this pull request
Apr 2, 2026
* chore: bump version to 0.6.0rc1 and add release marker * fix(test): extend nbval sanitize regex to match rc version suffixes The GAlgebra version pattern (-dev) didn't cover release candidates like 0.6.0rc1, causing nbval output mismatch failures in notebooks. * fix(docs): remove :release: marker from changelog for rc (semver incompatible) releases extension uses semantic_version which rejects '0.6.0rc1' (PEP 440 format, not semver). The release marker will be added as ':release:`0.6.0`' for the final release. The _version.py bump to 0.6.0rc1 controls PyPI. Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.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
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.
Summary
galgebra/_version.pyfrom0.6.0-devto0.6.0rc1:release:0.6.0rc1 <2026.04.01>`` marker todoc/changelog.rstRelease plan (after this PR is merged)
gh release create v0.6.0rc1 --prerelease --title "v0.6.0rc1" --notes "See [Changelog](https://galgebra.readthedocs.io/en/latest/changelog.html).\n\nhttps://pypi.org/project/galgebra/0.6.0rc1/"v0.6.0rc1tag + GitHub pre-release simultaneously0.6.0rc1to PyPINotes
_version.pymust match the tag name (lesson from 0.5.1 release: if_version.pysays0.5.1and you tagv0.5.1rc2, PyPI gets0.5.1not0.5.1rc2):release:0.6.0rc1→ `:release:`0.6.0in changelog and bump_version.pyto0.6.0