-
Notifications
You must be signed in to change notification settings - Fork 31
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
[ADD] Postgres 16 Support #18
base: master
Are you sure you want to change the base?
Conversation
Thank you so much ! |
Once this is merged that will definitely be possible, but I will not PR those changes myself as I don't use that template. |
@oskardotglobal Can you clean up this pr? Please remove unnessecary commits. |
You could base your PR on this 8179fde as it is analogous to what you want to do, but with Postgres 15. |
@bosd I will squash the commits. I seem to have removed V14 accidentally, I will readd this. @josep-tecnativa Thank you for the suggestion, but I think moving the build steps to actions from the python scripts is a much cleaner solution. I will still update the tests accordingly. |
a704d8e
to
3ef90d2
Compare
Sorry for the delay, but, Could you divide this PR in 2 commits? One fort testing and one for PG16 suport. Once this is made, I think it is ready to merge |
I don't think I can do that in a simple way; I've rewritten history in my local repo and force-pushed the remote |
@josep-tecnativa what about this? |
Since we needed to have PG 16 quickly, I made another PR and merged it. If you can modify this PR or create a new one with changes that are not related to PG 16, I will review it. |
After the chaos in #17 I decided to just PR this myself.
I'll have to make some changes, but this should be ready to go soon.