Skip to content

Provenance failed on publish, due to missing repo in sub-packages#162

Merged
khawkins merged 1 commit intoforcedotcom:mainfrom
khawkins:add_repo
Feb 12, 2026
Merged

Provenance failed on publish, due to missing repo in sub-packages#162
khawkins merged 1 commit intoforcedotcom:mainfrom
khawkins:add_repo

Conversation

@khawkins
Copy link
Copy Markdown
Collaborator

Still trying to fix OIDC issues. Next failure is:

npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access
npm notice publish Signed provenance statement with source and build information from GitHub Actions
npm notice publish Provenance statement published to transparency log: https://search.sigstore.dev/?logIndex=946248236
npm error code E422
npm error 422 Unprocessable Entity - PUT https://registry.npmjs.org/@salesforce%2fmagen-mcp-workflow - Error verifying sigstore provenance bundle: Failed to validate repository information: package.json: "repository.url" is "", expected to match "https://github.com/forcedotcom/mobile-mcp-tools" from provenance

So I'm creating the repository entries in the publishable packages.

@khawkins khawkins requested a review from a team as a code owner February 12, 2026 23:44
@khawkins khawkins merged commit 692dd5e into forcedotcom:main Feb 12, 2026
7 checks passed
@khawkins khawkins deleted the add_repo branch February 26, 2026 23:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant