Skip to content

Conversation

@PatrickSys
Copy link
Owner

What

  • Add automated Release PR generation (release-please)
  • Publish to npm only on version tags (v*) with a tag/package.json version guard
  • Add clear maintainer + contributor docs for the release flow

Why

  • Keep master always mergeable without auto-shipping on every PR
  • Make releases predictable (Release PR) and publishing fully automated (tag -> npm)

Notes

  • Requires repo secret NPM_TOKEN (already configured)

Adopt release-please for tagged releases and CI publishing; document the contributor/release workflow.
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.

Require @PatrickSys review for external PRs while allowing maintainers to self-merge when needed.
@PatrickSys PatrickSys merged commit e7f72cd into master Jan 28, 2026
3 checks passed
@PatrickSys PatrickSys deleted the chore/release-flow branch January 28, 2026 18:57
PatrickSys added a commit that referenced this pull request Jan 29, 2026
* chore(release): automate release PR + npm publish

Adopt release-please for tagged releases and CI publishing; document the contributor/release workflow.

* chore: add CODEOWNERS for maintainer approval

Require @PatrickSys review for external PRs while allowing maintainers to self-merge when needed.
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