- Notifications
You must be signed in to change notification settings - Fork15
Draft: Issue #139: Add PostgreSQL 18 builds to CI workflow#140
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Conversation
Hmmm, the CI workflow didn't run upon opening the merge request. @vitcpp : I think the CI workflows have been disabled. Can you re-enable them, please? |
@df7cb : Are you able to enable GitHub Actions on this repo? |
I only had admin rights on the "pgsphere" organization, not the postgrespro/pgsphere repo. |
Well, I just emailed@vitcpp. I hope he responds. I am concerned because he hasn't had any GitHub activity in almost a year. |
Hi@esabol, I'm here. I will review the patch and look at other new issues tomorrow. Sorry for the delay. Now it is too late. |
I enabled actions but not sure how to run them for the PR |
@esabol Could you please enable and run Build and Test workflow in your fork and branch to make sure everything is ok? I have no idea how to configure workflows in this repo to manually run with the specified PR? We will merge the commit if everything is ok. |
This merge request adds PostgreSQL 18 builds to the GitHub Action CI workflow. It's just a draft currently, because the goal is also to fix the selectivity regression test which has different output on PostgreSQL 18 in follow-up commits.