fix(publish): point repository.url at the renamed repo#123
Merged
Conversation
Every "Publish to npm" run on main has failed since the repository was renamed prisma/compose -> prisma/composer: sigstore provenance validation compares package.json repository.url against the repo the workflow actually ran in, strictly and without following GitHub redirects, and refuses the mismatch (npm E422). Both publishable manifests still pointed at the old name. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
wmadden-electric
enabled auto-merge
July 17, 2026 15:25
commit: |
wmadden
approved these changes
Jul 17, 2026
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
2 participants
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.
Every
Publish to npmrun on main has failed since the repo was renamedprisma/compose→prisma/composer— at least five runs today, predating #117. The failure:Provenance validation compares
repository.urlagainst the repository the workflow actually ran in — strictly, without following GitHub's rename redirect. Both publishable manifests still pointed at the old name; this updates the two URLs and nothing else (byte-targeted replacement, no manifest re-serialization).Verified locally:
pnpm lintexit 0,check-publish-depsexit 0. The publish itself can only be proven by the next main push — this PR merging is that push.🤖 Generated with Claude Code