Skip to content

use trusted publishing, not npm tokens#332

Merged
alexluckett merged 1 commit intomainfrom
trusted-publishing
Mar 6, 2026
Merged

use trusted publishing, not npm tokens#332
alexluckett merged 1 commit intomainfrom
trusted-publishing

Conversation

@alexluckett
Copy link
Contributor

@alexluckett alexluckett commented Mar 6, 2026

Proposed change

Moves us to use npm's trusted publishing feature. This removes the need for npm tokens.

Jira ticket:

Type of change

  • Bug fix
  • New feature
  • Breaking change
  • Misc. (documentation, build updates, etc)

Checklist

  • You have executed this code locally and it performs as expected.
  • You have added tests to verify your code works.
  • You have added code comments and JSDoc, where appropriate.
  • There is no commented-out code.
  • You have added developer docs in README.md and docs/* (where appropriate, e.g. new features).
  • The tests are passing (npm run test).
  • The linting checks are passing (npm run lint).
  • The code has been formatted (npm run format).

@alexluckett alexluckett enabled auto-merge March 6, 2026 16:04
@sonarqubecloud
Copy link

sonarqubecloud bot commented Mar 6, 2026

@alexluckett alexluckett merged commit 6050e7b into main Mar 6, 2026
24 checks passed
@alexluckett alexluckett deleted the trusted-publishing branch March 6, 2026 16:07
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