From bc5fff7b21527a1c46a6c9f0876cb4079143c1ca Mon Sep 17 00:00:00 2001 From: Eldon Marks Date: Tue, 7 Jul 2026 01:16:02 -0400 Subject: [PATCH] chore(release): bump to 0.0.12; skip-existing on PyPI publish 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 --- .github/workflows/publish.yml | 4 ++++ jvspatial/version.py | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml index c66511d..2632a0c 100644 --- a/.github/workflows/publish.yml +++ b/.github/workflows/publish.yml @@ -165,6 +165,10 @@ jobs: uses: pypa/gh-action-pypi-publish@release/v1 with: packages-dir: dist/ + # No-op (not a failure) when this version already exists on PyPI, so + # merges to main that don't bump the version don't red-X the branch. + # A real publish only happens when jvspatial/version.py is bumped. + skip-existing: true - name: Upload build artifacts uses: actions/upload-artifact@v7 diff --git a/jvspatial/version.py b/jvspatial/version.py index f1c5450..8dfbc53 100644 --- a/jvspatial/version.py +++ b/jvspatial/version.py @@ -9,4 +9,4 @@ # - MAJOR: Breaking changes # - MINOR: New features, backward compatible # - PATCH: Bug fixes, backward compatible -__version__ = "0.0.11" +__version__ = "0.0.12"