ci: pin the first postgrest-typegen release to 0.1.0

[spydon]

What

Release-please's first release PR for postgrest-typegen (#114) proposes 1.3.0 instead of 0.1.0. The component has no prior tag or release boundary, so release-please scanned the whole history and honored the old, unscoped root release commit chore: release 1.3.0 (#97, ee2ef6e) as an implicit Release-As override for the new component, even though that commit never touched packages/postgrest-typegen. Overrides win over the manifest bootstrap version.

This adds a temporary release-as: 0.1.0 pin so the first release matches the version already in the package's package.json. Release-please will regenerate #114 accordingly on its next run.

Follow-up

release-as in the config is sticky: it forces every release to 0.1.0 until removed. Remove it in a follow-up PR right after the regenerated #114 merges. #112 carries the same kind of pin for capability-matrix's first release (1.6.0) for the same reason.

[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: c1bacfa7-518e-416d-a106-7e9af7f617f9

---

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