Conversation
Replace the long-lived NPM_PUBLISH_TOKEN with npm trusted publishing: id-token permission, npm >= 11.5.1, --provenance, and a repository field on each published package (required to match the trusted publisher). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WUdwzfDSUhTEqqEWDhi6tB
shirish87
had a problem deploying
to
BrowserStackEnv
October 5, 2026 03:25 — with 
GitHub Actions
Error
GitHub Actions
Error
This branch was successfully deployed
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
2 participants
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.
Before: The Publish npm job authenticated with a long-lived
NPM_PUBLISH_TOKENsecret, which npm now rejects (main run #202 failed withE404on PUT).After: The job publishes with npm trusted publishing (OIDC), so no stored npm token is needed.
Changes the publish job to request
id-token: write, upgrade npm to >= 11.5.1, and runpnpm publish --provenancewithoutNODE_AUTH_TOKEN. Each published package also gets arepositoryfield, which npm checks against the trusted publisher.How: Before this works, each
@dot-slash/*package needs a trusted publisher configured on npmjs.com (Settings > Trusted Publisher: GitHub Actions, reposhirish87/browserstack-client, workflowmain.yml, environmentBrowserStackEnv). Not run end to end; verify by re-running the workflow on main after merging. 7.2.0 was never published, so no version bump is needed.🤖 Generated with Claude Code
https://claude.ai/code/session_01WUdwzfDSUhTEqqEWDhi6tB
Generated by Claude Code