Skip to content

Fix npm publish for scoped package releases - #68

Draft
alejouribesanchez with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-publish-npm-job
Draft

Fix npm publish for scoped package releases#68
alejouribesanchez with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-publish-npm-job

Conversation

Copilot AI commented Aug 4, 2026

Copy link
Copy Markdown

The publish-npm GitHub Actions job was failing during release publishing for @veryfi/veryfi-sdk. The workflow reached npm publish, but the publish request for the scoped package was not being sent with explicit public access.

  • Root cause

    • publish-npm used a plain npm publish for a scoped package.
    • npm requires explicit public access for publishing a public scoped package.
  • Workflow change

    • Updated the release publish step in .github/workflows/npm-publish.yml to publish with public access.
  • Resulting behavior

    • Keeps the existing trusted publishing/OIDC flow unchanged.
    • Ensures npm treats the release as a public publish for @veryfi/veryfi-sdk.
- run: npm publish --access public

Co-authored-by: alejouribesanchez <3950665+alejouribesanchez@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix failing GitHub Actions job publish-npm Fix npm publish for scoped package releases Aug 4, 2026
Copilot AI requested a review from alejouribesanchez August 4, 2026 20:28
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.

2 participants