Repository navigation
fix: set repository field on published packages for npm provenance - #112
Merged
Merged
Conversation
Trusted publishing generates a provenance attestation, and the registry rejects the publish (E422) unless package.json repository.url matches the GitHub repo that built it. None of the public packages declare one, so inject it at publish time alongside the scope rewrite.
setu4993
marked this pull request as ready for review
November 14, 2026 00:28
nishank-bhatnagar
approved these changes
Nov 14, 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
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
scripts/publish.mjsnow setsrepository(git+https://github.com/salesforce/agentscript.gitplus the package'sdirectory) on every non-private workspace package beforepnpm -r publish.package.jsonrepository.urlagainst the repo in that attestation. None of the public packages declarerepository, so the publish for fix: upgrade npm in publish workflow so trusted publishing works #111 failed with:@agentscript→@sf-agentscriptrewrite, so the internal → open source sync can't drop it. It also adds the repo link to the published packages on npmjs.com.Test plan
node --check scripts/publish.mjsdirectoryfor each; privatedocs,ui,vscodeand the root are skippedagentforce-dialect@2.88.3) withoutE422E404on other packages (would mean that package is missing its trusted publisher config)