Derive version from git tags via hatch-vcs#117
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The hatch-vcs dev version (X.Y.Z.devN+g<hash>) is long enough to wrap the welcome banner at 80 cols. Drop the tagline so the banner stays one line while --version/telemetry keep the full commit-identifying version. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The no-tag guard ran before the explicit-version branch, so 'cut_release.sh X.Y.Z' errored in a tagless repo despite explicit input being supported. Move the guard into the auto-bump branch and handle the no-tag status line. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
# Conflicts: # .gitleaks.toml
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.
What & why
Releases now derive the version from the git tag via
hatch-vcsinstead of hand-syncing a literal acrosspyproject.toml+aai_cli/__init__.py. Cutting a release collapses to pushing a tag — there is no version string to bump.Changes
pyproject.tomlusesdynamic = ["version"]+[tool.hatch.version] source = "vcs"with aversion-filehook that writes a gitignoredaai_cli/_version.py;aai_cli/__init__.pyre-exports__version__from it. Theuv lock --checkspike confirmed the lockfile does not drift on commits past a tag._version.py; mypy/pyright/import-linter accept it as-is.Formula/assembly.rb): the GitHub source tarball has no.git, sodef installfeeds the version via the genericSETUPTOOLS_SCM_PRETEND_VERSION(hatch-vcs 0.x doesn't honor the dist-scoped form) — installing resources under a clean env first, then setting it only for our package so resource versions aren't affected.scripts/bump_patch.sh; rewrotescripts/cut_release.shto derive the version from tags (no arg → next patch above the latest tag;cut_release.sh X.Y.Z→ explicit). All safety gates preserved. Dropped the deleted script fromcheck.sh's shellcheck list.X.Y.Z.devN+g<hash>) stays on one line;--version/telemetry keep the full commit-identifying version.generic-api-keyfalse positive on a kwarg expression instream_exec.py(version-skew between local and CI gitleaks).docs/superpowers/.Notes for reviewers
docs/superpowers/planning artifacts are included for traceability — say the word if you'd rather they not land in the repo.🤖 Generated with Claude Code