ci: release postgrest-typegen only on manual dispatch

[spydon]

Merging a postgrest-typegen change currently makes release-please open (or update) a release pull request right away, and merging that publishes to npm. This splits the package out of the automatic run so its releases are cut on demand instead.

What changed

• release-please-config.json / .release-please-manifest.json now cover only packages/capability-matrix. That run still fires automatically after Validate Capabilities on main.
• New release-please-config.postgrest-typegen.json / .release-please-manifest.postgrest-typegen.json cover packages/postgrest-typegen, seeded at the version currently on main (0.2.0).
• New Release postgrest-typegen workflow (workflow_dispatch only) runs release-please against that config and carries the npm publish job that used to live in release.yml.
• Both configs set separate-pull-requests: true so the two runs get component-scoped branches (release-please--branches--main--components--<component>) and cannot clobber each other.
• Short "Releasing" section in the package README describing the manual flow.

After merging

The currently open auto-created release pull request (#126) is on the old shared release-please--branches--main branch and will go stale. It should be closed; running Release postgrest-typegen recreates the equivalent pull request on the component-scoped branch whenever you want to cut 0.2.1.

[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: CHILL

Plan: Pro Plus

Run ID: 0fc2d0b0-6034-41c5-8de5-3b054932c036

---

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