Drop --provenance flag for private repo, bump to 0.2.5#18
Merged
sdserranog merged 1 commit intomainfrom Mar 5, 2026
Merged
Conversation
Provenance attestation requires a public source repository. OIDC trusted publishing auth works independently of --provenance. Add --provenance back when the repo is made public. Co-Authored-By: Claude Opus 4.6 <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
1 participant
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
--provenancefromnpm publish— provenance attestation requires a public source repo, but OIDC auth (Trusted Publishers) works without itNote
Add
--provenanceback when the repo is made public for supply chain attestation.Test plan
npm view @arcadeai/create-agent versionreturns0.2.5🤖 Generated with Claude Code