Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport to v12 #3646

Merged
merged 4 commits into from
Jul 9, 2024
Merged

Conversation

wolfgangwalther
Copy link
Member

Backports the fixes from #3639 and #3644 to v12.

I think we should make it a policy to backport fix commits immediately after merging them to main. We don't need to release on the backbranch immediately, but we should at least open the PR with the backport. This is because at this time, the changes are much more recent and easier to deal with in case they fail tests or so on the backbranch.

laurenceisla and others added 4 commits July 9, 2024 08:34
This needs to be loaded from in-database configuration first, otherwise
the dump-schema output will be for the default (public) schema.
There is no reason to hide those, right?
… present

The schema cache and OpenAPI output would currently list the first found
enum with the same name instead of the correct type. One other case
where this comes up is when a regular type and an enum type have the
same name. For example in the spec fixtures, we have an enum called
"bit". Every "bit" type, no matter whether it's that enum or the
built-in bit type, will show those enum options in the OpenApi output.

Not adding a test, because OpenAPI is supposed to go away in the future
anyway.
@wolfgangwalther wolfgangwalther merged commit 9a40bc2 into PostgREST:v12 Jul 9, 2024
25 checks passed
@wolfgangwalther wolfgangwalther deleted the backport-fixes branch July 9, 2024 07:09
@steve-chavez
Copy link
Member

I think we should make it a policy to backport fix commits immediately after merging them to main

Fully agree with that.

@steve-chavez
Copy link
Member

Any reason why shouldn't we release a new patch version now? The fixes and the perf increase are really good.

@wolfgangwalther
Copy link
Member Author

Any reason why shouldn't we release a new patch version now? The fixes and the perf increase are really good.

Patch release? Sure, go ahead.

The performance commit is not a fix, though, and thus not backpatched. It's only part of main. I sure don't want to release a major now, we might have more breaking changes to consider before doing that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants