chore(release): 0.3.0 (leave the beta dist-tag)

[simoncrypta]

Beads: cedar-pg-js5

Release

This cuts @cedarjs/pg 0.3.0 and moves off the beta dist-tag.

It's a 0.x minor bump instead of 0.2.0-beta.2 because this release breaks two contracts:

• role and clone naming for long worktree names (fix(naming): keep full mode + hash in role and clone names #44, with the upgrade-safe lease role from fix(acquire): keep the lease's role for the same database #51);
• cedarpg run exit codes on signals (fix(run): forward SIGINT/SIGTERM/SIGHUP to the child and exit 128+signal #46).

1.0.0 comes once the API settles.

Version and dist-tag

• package.json: version 0.2.0-beta.1 → 0.3.0, and publishConfig.tag beta → latest.
• I set it to latest instead of removing it. publish.yml derives latest from a plain version and fails when publishConfig.tag doesn't match, so both paths agree.
• I checked this locally: version 0.3.0, configured tag latest, derived tag latest.

Docs

• README: the status line now reads pre-1.0 (0.x, latest dist-tag), and APIs may still change between minor versions. The install commands are plain @cedarjs/pg instead of @beta.
• AGENTS.md: the same wording.
• src/core/lifecycle.ts: a comment now says 0.3.0 instead of 0.2.0-beta.2.

CHANGELOG highlights (## Unreleased → ## 0.3.0)

• Leaves the beta dist-tag; npm install @cedarjs/pg installs it as a normal 0.x release.
• cedarpg run --attach, an attach-only child run for the Nx db:ready shape. @cedarjs/pg/nx is removed.
• TEMPLATE workers:
  • worker clones are reused across files, backed by the database;
  • each file starts on truncated tables with RESTART IDENTITY;
  • setup starts clean (fresh);
  • workers attach via the lease port, with no host discovery per file.
• Role and clone names keep the full _<mode>_<pathHash8>, so long-named worktrees no longer share a role. Existing leases keep their stored role.
• cedarpg run / studio forward SIGINT, SIGTERM and SIGHUP, and exit with 128 + n when the child is killed by a signal.
• autopg pin is now v3.2.2, with an outdated-autopg warning. Ephemeral CI cold starts are serialized with a lock and no longer delete /dev/shm/PostgreSQL.* segments.
• The Vite+ dev example uses cedarpg run --attach, and the no-op acquire --force is gone from the docs.

Inside the cut section, "this release" now reads "0.3.0", and two stray blank lines that split bullet lists are gone. Past sections are untouched.

The heading is ## 0.3.0 with no date, matching the existing headings. An empty ## Unreleased stays above it, as in the 0.2.0-beta.1 cut.

Checks

• vp check: pass
• vp test: pass, 22 files / 138 tests
• vp run smoke: pass (packs cedarjs-pg-0.3.0.tgz)
• vp run smoke:pg: pass

No tag or publish yet; that happens after merge through publish.yml.

🤖 Generated with Claude Code

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: d6a4cd1d-8ed0-4f01-8bd5-4d53b428c852

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@cedarjs/pg@52

commit: 2b9f7ca