Skip to content

ci: fix pnpm publish to use OIDC trusted publishing with provenance #1451

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AbhiPrasad merged 1 commit into from
Feb 27, 2026
Merged

ci: fix pnpm publish to use OIDC trusted publishing with provenance #1451

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion js/Makefile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -152,7 +152,7 @@ publish-sdk-js:
./scripts/validate-release.sh
pnpm install
pnpm run build
pnpm publish --no-git-checks
pnpm publish --no-git-checks --provenance

# This is the only method I could find to install a package without explicitly
# adding a dependency or modifying lock files.
Expand Down
2 changes: 1 addition & 1 deletion js/scripts/publish-prerelease.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ echo ""
# In CI, just publish. Locally, ask for confirmation
if [ -n "${CI:-}" ] || [ -n "${GITHUB_ACTIONS:-}" ]; then
# Running in CI - publish without confirmation
pnpm publish --tag "$DIST_TAG" --no-git-checks
pnpm publish --tag "$DIST_TAG" --no-git-checks --provenance
else
# Running locally - ask for confirmation
read -p "Ready to publish version $NEW_VERSION to npm with tag @$DIST_TAG? (y/N) " -n 1 -r
Expand Down
Loading