Files
probo/contrib/claude/release/prb.md
Bryan Frimin ac526fb54d Split release into per-track packages
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>
2026-05-06 16:04:36 +02:00

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 only X.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

  1. From a clean main, list commits since the last prb tag:

    git log $(git describe --tags --abbrev=0 --match='prb/v*')..HEAD --oneline \
      -- cmd/prb pkg/cli pkg/cmd
    

    If the list is empty (or contains only non-user-facing commits), do not release this track.

  2. Decide the version bump (PATCH for fixes, MINOR for features).

  3. Bump the version in cmd/prb/VERSION (the file contains a single X.Y.Z line — no trailing newline conventions beyond what is already there).

  4. Write the new entry in cmd/prb/CHANGELOG.md following the rules in README.md.

  5. Show the user the changelog diff and the new version. Wait for confirmation.

  6. Stage only cmd/prb/VERSION and cmd/prb/CHANGELOG.md. Commit subject: Release prb/v<version>. No body.

  7. Annotated tag: git tag -a prb/v<version> -m "prb/v<version>".

  8. 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.