Canonicalize URLs to siftfy/ org after repo transfer#3
Merged
Conversation
Repo moved from GipsyChef/siftfy-python to siftfy/siftfy-python. GitHub auto-redirects, but the PyPI project page surfaces [project.urls] verbatim — and the README CI badge bakes the path into the badge image — so update both to the canonical owner. The next tagged release will republish to PyPI with the new URLs; existing pinned versions (0.1.0) retain the old URLs in their metadata, which is fine: GitHub redirects keep the links live. Reminder: PyPI Trusted Publisher Owner field also needs to be updated from GipsyChef to siftfy in the project's Publishing settings, otherwise the next release will fail OIDC trust. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
The repo was just transferred from `GipsyChef/siftfy-python` to `siftfy/siftfy-python`. GitHub auto-redirects, but two things bake the path in:
Updating both. The next tagged release will republish with canonical URLs; older pinned versions on PyPI keep the old metadata, which is fine since GitHub redirects.
Reminder for the maintainer
The PyPI Trusted Publisher (OIDC) configuration on `pypi.org/project/siftfy` is currently bound to `GipsyChef/siftfy-python`. Update the Owner field to `siftfy` before the next `git tag v0.x.x` push — otherwise the publish workflow will fail with an OIDC trust mismatch (silently, since the workflow only runs on tag push).
PyPI → `siftfy` project → Manage → Publishing → edit the trusted publisher.
🤖 Generated with Claude Code