Each shippable artifact (prb, probod server group, probod-bootstrap, @probo/n8n-nodes-probo, @probo/cookie-banner) now has its own version file, its own CHANGELOG.md, its own annotated-tag scheme of the form <track>/v<version>, and its own GitHub Actions release workflow. The unified release.yaml is removed; the unified CHANGELOG.md becomes a short index pointing at each per-track file, with the prior history preserved in CHANGELOG.archive.md. Probod's CHANGELOG carries the post-split monorepo releases (0.174.0 through 0.181.0) so the server-group history stays continuous and the probod docker image keeps its existing version line. contrib/claude/release.md is split into contrib/claude/release/ with one entrypoint per track plus a README that drives the agent: detect which tracks have user-facing commits since their last tag and skip tracks with no relevant changes, so a release request never tags an unchanged track. The cookie-banner and n8n-node entrypoints add an explicit npm run build step after the version bump (build.mjs bakes package.json's version into __SDK_VERSION__) so compile errors and package-lock.json updates are caught before tagging. Signed-off-by: Bryan Frimin <bryan@getprobo.com>
1.5 KiB
Release prb (CLI)
Entrypoint for releasing the prb CLI. Read README.md
first for overall flow, changelog rules, and the
non-empty-track guarantee.
Track facts
- Tag pattern:
prb/v* - Version source:
cmd/prb/VERSION(contains onlyX.Y.Z) - Changelog:
cmd/prb/CHANGELOG.md - Workflow:
.github/workflows/release-prb.yaml - Path filter (for log/scoping):
cmd/prb pkg/cli pkg/cmd
Steps
-
From a clean
main, list commits since the lastprbtag:git log $(git describe --tags --abbrev=0 --match='prb/v*')..HEAD --oneline \ -- cmd/prb pkg/cli pkg/cmdIf the list is empty (or contains only non-user-facing commits), do not release this track.
-
Decide the version bump (PATCH for fixes, MINOR for features).
-
Bump the version in
cmd/prb/VERSION(the file contains a singleX.Y.Zline — no trailing newline conventions beyond what is already there). -
Write the new entry in
cmd/prb/CHANGELOG.mdfollowing the rules in README.md. -
Show the user the changelog diff and the new version. Wait for confirmation.
-
Stage only
cmd/prb/VERSIONandcmd/prb/CHANGELOG.md. Commit subject:Release prb/v<version>. No body. -
Annotated tag:
git tag -a prb/v<version> -m "prb/v<version>". -
Push:
git push origin main --follow-tags.
CI workflow release-prb.yaml builds binaries for 9 OS/arch targets,
publishes a GitHub Release, and updates the Homebrew formula at
getprobo/homebrew-tap.