ci: drop release-as pins so release-please computes versions from commits

[spydon]

Summary

Removes the release-as entries from release-please-config.json for both packages.

release-as pins every release PR to that exact version. The pins were used to force the initial versions when the per-package release-please setup landed (#111/#112), but both packages have since shipped those versions (capability-matrix 1.6.0, postgrest-typegen 0.1.0), so the pins now block any further version bump.

Concretely: #118 landed as a feat on postgrest-typegen, which with bump-minor-pre-major: true should produce 0.2.0, but the release PR #119 proposed a no-op v0.1.0...v0.1.0 release with only a changelog change because the config forced 0.1.0 again. capability-matrix would hit the same wall on its next release.

Once this merges, release-please will refresh #119 to a proper 0.2.0 (changelog, package.json, and manifest bump).

Test plan

• release-please-config.json still validates against its $schema (structure unchanged, only the two release-as keys removed)
• After merge: release-please refreshes chore: release main #119 to postgrest-typegen: 0.2.0

[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: cfbb0466-07ec-49c5-ac6b-9e902c60defe

---

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