Skip to content

Bump to 0.1.1 — validate new PyPI Trusted Publisher#4

Merged
cigan1 merged 1 commit into
mainfrom
release/v0.1.1
May 5, 2026
Merged

Bump to 0.1.1 — validate new PyPI Trusted Publisher#4
cigan1 merged 1 commit into
mainfrom
release/v0.1.1

Conversation

@cigan1

@cigan1 cigan1 commented May 5, 2026

Copy link
Copy Markdown
Contributor

Summary

No-op release whose purpose is to exercise the new `siftfy/siftfy-python` PyPI Trusted Publisher end-to-end before we delete the old `GipsyChef/...` trusted-publisher row.

What this does

  • Bumps `version` to `0.1.1` in both `src/siftfy/_version.py` and `pyproject.toml` so the workflow's tag-matches-package-version check passes.
  • Side benefit: re-publishes the package's `[project.urls]` to PyPI with the canonical `siftfy/` URLs (which were canonicalized in Canonicalize URLs to siftfy/ org after repo transfer #3 but won't surface on the PyPI project page until a new release).

Release flow

  1. Merge this PR.
  2. `git tag v0.1.1` on `main` and push the tag.
  3. The `Publish to PyPI` workflow runs, exchanges OIDC for a PyPI upload token via Trusted Publisher.
  4. If the new trust is wired correctly: 0.1.1 lands on PyPI and we delete the `GipsyChef` row.
  5. If trust fails: workflow fails the publish step. We leave both rows in place and debug.

🤖 Generated with Claude Code

No code change. The repo was just transferred from GipsyChef/ to
siftfy/, and PyPI Trusted Publisher trust was reconfigured to bind
the OIDC token claim to the new owner. This release exists solely
to exercise that trust end-to-end before deleting the old (now-dead)
GipsyChef trusted-publisher row from PyPI.

The 0.1.1 release also re-publishes [project.urls] with canonical
siftfy/ URLs (pyproject.toml was canonicalized in #3 but 0.1.0's
PyPI metadata is frozen with the old URLs).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@cigan1 cigan1 merged commit 51cac6a into main May 5, 2026
5 checks passed
@cigan1 cigan1 deleted the release/v0.1.1 branch May 5, 2026 00:02
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