fix: add repository field to published packages#2941
Merged
chanceaclark merged 1 commit intocanaryfrom Mar 20, 2026
Merged
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
npm's sigstore provenance verification requires package.json to have a repository.url matching the GitHub repository. Without this field, changeset publish fails with E422 for all published packages. Co-Authored-By: Claude <noreply@anthropic.com>
chanceaclark
force-pushed
the
NO-TICKET/fix/add-repository-field-to-published-packages
branch
from
90205f7 to
d19a928
Compare
Contributor
Bundle Size ReportComparing against baseline from No bundle size changes detected. |
rtalvarez
approved these changes
Mar 20, 2026
bc-alexsaiannyi
approved these changes
Mar 20, 2026
chanceaclark
deleted the
NO-TICKET/fix/add-repository-field-to-published-packages
branch
chanceaclark
added a commit
that referenced
this pull request
Apr 27, 2026
npm's sigstore provenance verification requires package.json to have a repository.url matching the GitHub repository. Without this field, changeset publish fails with E422 for all published packages. Co-authored-by: Claude <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
3 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.
What/Why?
npm's sigstore provenance verification requires
package.jsonto include arepository.urlthat matches the GitHub repository URL. Without this,changeset publishfails withE422 Unprocessable Entityfor all published packages.Adds the
repositoryfield (withdirectoryfor monorepo support) to:@bigcommerce/create-catalyst@bigcommerce/catalyst-client@bigcommerce/eslint-config-catalystRollout/Rollback
No rollout needed — metadata-only change. Rollback is a simple revert.
Testing
Verify each published
package.jsonhas a validrepositoryfield:jq '.repository' packages/create-catalyst/package.json packages/client/package.json packages/eslint-config-catalyst/package.json