Repository navigation
Release 1.0.0: package version matches the tag - #9
Merged
Merged
Conversation
…lone pyproject still said 0.1.0 while paths.TAG and every setup cell say v1.0.0. A test now holds the two together; it was watched to fail at 0.1.0. Co-Authored-By: Claude Opus 5.5 <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
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.
pyproject.tomlsaid0.1.0whilepaths.TAGand all twenty-two setup cells sayv1.0.0. This sets it to1.0.0and addstest_the_package_version_is_the_tag_the_notebooks_clonetotests/test_paths.py, so the two can't drift again (watched to fail at0.1.0). The README's "Cutting a release" step 1 now names pyproject too.After merge: annotated tag
v1.0.0on the merge commit, checked to peel. No GitHub Release.🤖 Generated with Claude Code