Skip to content

Conversation

@PatrickSys
Copy link
Owner

What

  • Publish to npm directly from the Release Please workflow when a release is created
  • Remove separate tag-triggered Publish workflow

Why

  • Tags/releases created by workflows using GITHUB_TOKEN do not trigger other workflows.
  • Keeping publish inside the same Release Please run makes publishing fully automated without extra PAT secrets.

Avoid relying on tag-triggered workflows (which don't run when tags are created via GITHUB_TOKEN) by publishing in the same release-please run.
Copy link

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

@PatrickSys PatrickSys merged commit 0a9a325 into master Jan 28, 2026
3 checks passed
@PatrickSys PatrickSys deleted the chore/release-publish-unify branch January 28, 2026 19:11
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