Skip to content

Change NPM token secret for release workflow#231

Merged
lfarrel6 merged 1 commit intomasterfrom
fix/patch-npm-token-for-release
Mar 3, 2026
Merged

Change NPM token secret for release workflow#231
lfarrel6 merged 1 commit intomasterfrom
fix/patch-npm-token-for-release

Conversation

@lfarrel6
Copy link
Member

@lfarrel6 lfarrel6 commented Mar 3, 2026

Why

Incorrect secret being used for npm publish caused workflow to fail

How

Standardize to common secret.

@changeset-bot
Copy link

changeset-bot bot commented Mar 3, 2026

⚠️ No Changeset found

Latest commit: 98192cd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@lfarrel6 lfarrel6 merged commit ef1320b into master Mar 3, 2026
8 checks passed
@lfarrel6 lfarrel6 deleted the fix/patch-npm-token-for-release branch March 3, 2026 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants