Skip to content

Fix npm publish on merge to master - #148

Merged
esitarz merged 1 commit into
masterfrom
ex-3857-js-sdk-publish-fix
Sep 25, 2026
Merged

esitarz merged 1 commit into
masterfrom
ex-3857-js-sdk-publish-fix

Conversation

@esitarz

@esitarz esitarz commented Sep 25, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Point setup-node at the npm registry so NPM_TOKEN is actually used
  • Write the changelog body as a multiline Actions output so the GitHub release step receives it
  • Run npm publish only when action-autotag created a new tag, so later pushes of the same version do not fail the workflow

Test plan

  • Merge a version-bump PR and confirm Tag, Release, & Publish creates the release and publishes to npm
  • Push a master commit that does not change package.json version and confirm the workflow succeeds without publishing

Authenticate to the npm registry, keep the changelog body intact, and skip publish when the version tag already exists.
@esitarz esitarz mentioned this pull request Sep 25, 2026
2 of 4 tasks
@esitarz
esitarz merged commit ddb48b6 into master Sep 25, 2026
1 check passed
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