Repository navigation
Point extras install commands at the release tag until PyPI is live - #20
Merged
Merged
Conversation
The bare 'shimkit[extra-tools]' form resolves against PyPI, where every publish-pypi run since v0.11.0 has failed with invalid-publisher because no trusted publisher is registered on pypi.org. The shipping checklist still listed the pypi environment as missing (it exists) and suggested re-running failed jobs whose build artifacts have since expired.
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.
Why
https://pypi.org/pypi/shimkit/jsonanswers 404. Everypublish-pypirun from v0.11.0 through v0.19.0 failed the OIDC token exchange withinvalid-publisher: valid token, but no corresponding publisher. The token carriedsub: repo:simtabi/shimkit:environment:pypiandworkflow_ref: .../release.yml@refs/tags/vX.Y.Z, so the workflow and thepypienvironment are correct; pypi.org has no trusted publisher registered. That is an owner action, not a code change.Meanwhile some docs assumed PyPI:
docs/installation.mdextras commands (uv tool install 'shimkit[extra-tools]') resolve against PyPI and fail. They now name the release tag as a direct reference.docs/shipping-checklist.mdlisted thepypienvironment as missing (it exists) and suggested "Re-run failed jobs" for past tags. Those runs'distartifacts have expired, so the checklist now says to dispatchrelease.ymlon the tag instead.There is no PyPI badge in the README, so no badge change is needed.
Changes
README.md,docs/installation.md: extras commands use'shimkit[extra-tools] @ git+https://github.com/simtabi/shimkit@v0.19.0'.docs/shipping-checklist.md: 2.4 marked done with evidence; 4.2 named as the only blocker; republish path corrected.CHANGELOG.md: Unreleased / Fixed entry.Docs only. No workflow or code change.