chore(release): bump to 0.0.12; skip-existing on PyPI publish#28
Merged
Conversation
The publish-on-push workflow re-uploaded the unchanged 0.0.11 on every merge to main (incl. #26/#27), failing with `400 File already exists`. Two fixes: - Bump __version__ 0.0.11 -> 0.0.12 to release the postgres translator column-index fix + observability env keys. - Add `skip-existing: true` to the pypa/gh-action-pypi-publish step so future merges that don't bump the version are a no-op success instead of a red X. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Benchmark comparisonThreshold: ±25% (informational, does not block merge)
|
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.
Problem
The publish-on-push workflow re-uploads the current package version on every merge to
main. Since__version__stayed at0.0.11(already on PyPI), merges #26 and #27 failed the Publish to PyPI job with400 File already exists ('jvspatial-0.0.11-...'). Test / Benchmarks / Lint all pass — only publish was red.Fix
__version__0.0.11 → 0.0.12 — releases the postgres translator column-index fix (entity/id/tenant_idhit real indexed columns, not JSONB paths) + the observability env keys from fix(postgres): translate entity/id/tenant_id to real columns; register observability env keys #27.skip-existing: trueon thepypa/gh-action-pypi-publishstep — a merge that doesn't bump the version becomes a no-op success instead of red-X'ingmain; a real upload happens only whenversion.pyis bumped.Test plan
pre-commit runclean (black, isort, flake8, mypy, detect-secrets).🤖 Generated with Claude Code