Skip to content

fix(build): add npm provenance to all package publishConfig - #5228

Merged
robert-hebel-sb merged 2 commits into
mainfrom
fix/publish-provenance
Sep 4, 2026
Merged

robert-hebel-sb merged 2 commits into
mainfrom
fix/publish-provenance

Conversation

@robert-hebel-sb

Copy link
Copy Markdown
Contributor

No description provided.

@robert-hebel-sb robert-hebel-sb added the bug Something isn't working label Sep 4, 2026
@robert-hebel-sb
robert-hebel-sb merged commit 5437816 into main Sep 4, 2026
9 checks passed
@robert-hebel-sb
robert-hebel-sb deleted the fix/publish-provenance branch September 4, 2026 08:41
robert-hebel-sb added a commit that referenced this pull request Sep 8, 2026
…5230)

Provenance generation requires "write" access to the "id-token"
permission. The release-to-GPR workflow was missing this permission
block entirely, which causes lerna publish to fail when publishConfig
has provenance enabled.

Related to #5228
robert-hebel-sb added a commit that referenced this pull request Sep 10, 2026
…5230)

Provenance generation requires "write" access to the "id-token"
permission. The release-to-GPR workflow was missing this permission
block entirely, which causes lerna publish to fail when publishConfig
has provenance enabled.

Related to #5228
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants