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

Update version to 0.12.5 #1883

Merged

Conversation

eeeebbbbrrrr
Copy link
Contributor

@eeeebbbbrrrr eeeebbbbrrrr commented Sep 26, 2024

Welcome to pgrx v0.12.5. This is a big minor release because it brings support for Postgres v17.0, released on Sept 26th, 2024. Much thanks to the Postgres folks for all their hard work! We'd have to do this for MySQL otherwise!

To upgrade to pgrx v0.12.5, do cargo install cargo-pgrx --version 0.12.5 --locked. Once installed you can run cargo pgrx upgrade in the root of all your extension crates to update their dependencies.

New Features

pgrx now supports Postgres v17.0! You'll want to run another cargo pgrx init to get the latest release of all Postgres versions, including 17.

diffs between schema versions should be a lot prettier now as cargo pgrx schema should be repeatable from run-to-run and otherwise output in a predictable order.

Regular and cross-compiles should be more reliable now thanks to using cc to compile the tiny bit of C code pgrx includes.

Made with love to those who don't like allocations!

Bug Fixes

More Postgres Headers

Docs & Examples

Code Cleanup

New Contributors

Full Changelog: v0.12.4...v0.12.5

@YohDeadfall
Copy link
Contributor

@eeeebbbbrrrr, want to include #1879?

@eeeebbbbrrrr
Copy link
Contributor Author

@eeeebbbbrrrr, want to include #1879?

Lets wait for @workingjubilee's approval on that. I'm happy to another release tomorrow or over the weekend or whenever. I want you to have access to your work as quickly as reasonable.

@eeeebbbbrrrr eeeebbbbrrrr merged commit 2801296 into pgcentralfoundation:develop Sep 26, 2024
14 checks passed
@YohDeadfall
Copy link
Contributor

I want you to have access to your work as quickly as reasonable.

For that reason I switched to a local reference (:

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

Successfully merging this pull request may close these issues.

2 participants