Skip to content

ci(release): release with release-please - #41

Merged
StefanoGuerrini merged 1 commit into
mainfrom
ci/release-please
Oct 14, 2026
Merged

StefanoGuerrini merged 1 commit into
mainfrom
ci/release-please

Conversation

@StefanoGuerrini

Copy link
Copy Markdown
Contributor

Summary

Releases now come from release-please. Merging the chore: release X.Y.Z PR releases: the workflow checks and builds with read-only rights, then creates the tag and the GitHub release with generated notes, and publishes to npm with trusted publishing.

What changes for maintainers

  • PR titles must be Conventional Commits. fix, feat and perf need a lowercase scope, for example fix(crawl): .... They set the version: fix patch, feat minor, ! major.
  • Only fix, feat, perf and revert PRs lead to a release. docs, chore, test, ci, refactor, build and style do not.
  • Do not change the version by hand. release-please sets it.
  • A new check rejects trailer lines, issue tracker keys and AI attribution in PR titles, bodies, branch names and commit messages.
  • Changes to .github/ and release-please-config.json need a review from @ZenRows/prod-approvers.

Notes

  • The manifest starts at 1.5.3, the latest release.
  • This is the first release from CI. release-please also updates CLI_VERSION in src/core/config.ts; the version script is removed.

The CLI was versioned and published to npm by hand. release-please now
opens a release PR from Conventional Commit titles and sets the version in
package.json, package-lock.json and CLI_VERSION. Merging that PR tags,
creates the GitHub release and publishes to npm with trusted publishing.
The npm version script and its sync script are no longer needed.
@ZenRows ZenRows deleted a comment from linear Bot Oct 14, 2026
@StefanoGuerrini
StefanoGuerrini marked this pull request as ready for review October 14, 2026 10:33
@StefanoGuerrini
StefanoGuerrini merged commit a7098ab into main Oct 14, 2026
3 checks passed
@StefanoGuerrini
StefanoGuerrini deleted the ci/release-please branch October 14, 2026 10:34
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.

1 participant