Skip to content

Conversation

@ramsunvtech
Copy link
Member

What

Fixes npm authentication in the GitHub Actions pipeline so semantic-release can
fully automate versioning, tagging, GitHub releases, and npm publishing.

Why

semantic-release was failing during the npm verification step due to missing
explicit npm authentication, resulting in E401 (Unauthorized) errors and no
published releases.

Changes

  • Explicitly configure npm authentication using NPM_TOKEN
  • Ensure semantic-release can:
    • Bump version automatically
    • Create git tags
    • Create GitHub releases
    • Publish packages to npm
  • Keep release fully automated with no manual version changes

How to test

  1. Merge this PR into the release branch
  2. Push a commit with a Conventional Commit message (e.g. feat: or fix:)
  3. Verify:
    • New git tag is created
    • GitHub release is published
    • Package is published to npm

Notes

  • Requires a valid npm Automation token with publish access
  • 2FA must be set to Authorization only

Release - 19th Jan 2026
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.

3 participants