Skip to content

Use dynamic (hatch-vcs) versioning instead of a hardcoded version - #74

Merged
ryanmrichard merged 1 commit into
masterfrom
dynamic-version
Aug 11, 2026
Merged

Use dynamic (hatch-vcs) versioning instead of a hardcoded version#74
ryanmrichard merged 1 commit into
masterfrom
dynamic-version

Conversation

@ryanmrichard

Copy link
Copy Markdown
Member

Summary

  • deploy_to_pypi runs on every push to master, but pyproject.toml pinned version = "0.1.0", so every deploy after the first successful publish failed with 400 Bad Request: File already exists.
  • Switches to hatch-vcs for dynamic, git-tag-derived versioning — the pure-Python (hatchling) equivalent of what every other NWChemEx repo does via setuptools_scm.

Test plan

  • Built sdist + wheel locally in an isolated venv; version was correctly derived from git tags instead of the fixed 0.1.0.
  • Confirm the merge workflow publishes successfully to PyPI after this merges (the tag-commit job creates the new tag before deploy_to_pypi checks out, so the wheel picks it up).

🤖 Generated with Claude Code

Every push to master triggers a PyPI publish, but the version was
pinned to 0.1.0, so every deploy after the first succeeded failed
with "400 File already exists". Switch to hatch-vcs, matching how
every other NWChemEx repo derives its version from git tags.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@ryanmrichard
ryanmrichard merged commit 98e7923 into master Aug 11, 2026
8 checks passed
@ryanmrichard
ryanmrichard deleted the dynamic-version branch August 11, 2026 13:46
@github-actions

Copy link
Copy Markdown

🚀 [bumpr] Bumped!
New version:v0.0.12
Changes:v0.0.11...v0.0.12

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant