Reset version line to 0.2.0 (skip orphaned 0.1.0) - #85
Merged
Merged
Conversation
nwchemex-nwxcmake==0.1.0 on PyPI is an orphaned build-overhaul-era snapshot with no git tag, hardcoding a since-deleted simde branch. Every ecosystem repo's pyproject.toml pins >=0.1.0, so pip always resolved to that broken release over any newer 0.0.x fix. Bumping to 0.2.0 (via a v0.1.99 sentinel tag, see this PR's bump:minor label) gets those pins resolving to a real, current release again.
ryanmrichard
added
the
bump:minor
Pre-existing whitespace in comments from this week's self-override work; caught while getting this PR's check_formatting job to pass.
jwaldrop107
approved these changes
Sep 11, 2026
|
🚀 [bumpr] Bumped! |
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.
Summary
nwchemex-nwxcmake==0.1.0release (2026-08-05, no git tag) that hardcodes a since-deletedsimdegit branch (build_overhaul).pyproject.tomlpinsnwchemex-nwxcmake>=0.1.0, so pip always resolves to that broken release instead of any newer0.0.xfix (currently0.0.26, which contains this week's integration-testing self-override fix).v0.1.99sentinel git tag (no PyPI release) was pushed tomasterso this PR'sbump:minorlabel lands the next release exactly on0.2.0, skipping the poisoned0.1.xline entirely -- no pin changes needed in any downstream repo.Test plan
bump:minorlabel attachedmerge.yamltagsv0.2.0and publishesnwchemex-nwxcmake==0.2.0to PyPIpip install "nwchemex-nwxcmake>=0.1.0"now resolves to0.2.0🤖 Generated with Claude Code