-
Notifications
You must be signed in to change notification settings - Fork 105
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
python/adbc_driver_postgresql: integration tests are failing #1333
Comments
I think this started with this upstream PR in polars: It looks like in arrow-adbc we are driving the release number off of what
But it looks like the tags that exist don't exist on the main branch, and the commits they reference are on the maintenance branches (were these cherry-picked?) so when building from source you always end up with version Is it intentional for tags not to exist on the main branch or a msitake? |
Ah...That is how the release process works (using maintenance branches), which is a holdover from the main Arrow project (which creates a branch and cherry-picks commits onto it as needed). So either we can adjust CI to force/fake a particular version, or we could consider just releasing directly off of main. |
I don't think this is the better long term option of what is described in #1333 (comment) but should get CI green for now
So continuing from #1337 we should set SETUPTOOLS_SCM_PRETEND_VERSION in our various pipelines and have the bump-version release script update this. |
Closing in favor of #1363 |
The text was updated successfully, but these errors were encountered: