Skip to content

chore: release main - #119

Closed
supabase-releaser[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main
Closed

chore: release main#119
supabase-releaser[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@supabase-releaser

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

postgrest-typegen: 0.1.0

0.1.0 (2026-08-31)

Features

  • postgrest-typegen: formatter hook, oxfmt default, concurrent introspection (#118) (fa2286c)

This PR was generated with Release Please. See documentation.

@supabase-releaser
supabase-releaser Bot force-pushed the release-please--branches--main branch from 2aa1543 to 7c6f82e Compare August 31, 2026 11:46
@spydon

spydon commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Closing since version was pinned.

@spydon spydon closed this Aug 31, 2026
spydon added a commit that referenced this pull request Aug 31, 2026
…mits (#120)

## 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

- [x] `release-please-config.json` still validates against its $schema
(structure unchanged, only the two `release-as` keys removed)
- [ ] After merge: release-please refreshes #119 to `postgrest-typegen:
0.2.0`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant