Skip to content

Configure npm auth for publish workflow #32

@nillo

Description

@nillo

The v1.1.0 release workflow reached npm publish on commit 066597f after package gates passed, but failed with ENEEDAUTH because NODE_AUTH_TOKEN was empty.

Evidence:

  • Workflow: Publish to npm, run 26001744009
  • .github/workflows/publish.yml uses ${{ secrets.NPM_TOKEN }}
  • GitHub logs show NODE_AUTH_TOKEN: empty
  • Local npm publish --access=public passed prepublish/package gates and reached npm, then failed only with EOTP requiring a human OTP

Fix options:

  • Add a valid NPM_TOKEN repository secret with publish rights, or
  • Configure npm trusted publishing/OIDC for this package and update the workflow accordingly.

After fixing auth, re-run publish for the current v1.1.0 release/tag or publish locally with OTP.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions