-
Notifications
You must be signed in to change notification settings - Fork 23
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
Release version 0.8.0 #410
Comments
Would be nice to get #411 , but that is oriented at tests and can happen whenever - it just needed to happen at a time when we didn't have a lot of outstanding PRs where it would cause git conflicts. Otherwise agreed, finally ready for 0.8! |
I suppose we should then pin geopandas to 0.8, right? Given the recent PRs. |
Released! https://github.com/geopandas/pyogrio/releases/tag/v0.8.0 Wheels on PyPI. |
Thank @brendan-ward!
Not necessarily? Yes you need the latest version if you want to write to BytesIO, but I don't know if that is enough reason to force everyone to have the latest version? (eg for conda-forge, pyogrio is only built with the latest GDAL, so if you have a bigger environment that for some reason still needs a previous build of gdal, then that might be a bit annoying?) |
@brendan-ward I got a notification from PyPI that an API token was used to upload files to the project, even though the project has a Trusted Publisher configured. They say
Was the setup of Trusted Publisher finished on GHA side? |
Sorry, I should have logged a note about that since this was the first time we've gotten notifications. We have a Trusted Publisher setup for GitHub, but that is not available for CircleCI (where we build linux Arm64 wheels), so our current deploy workflow involved downloading those wheels from CircleCI and uploading manually (using personal accounts) to PyPI. |
Let's release?
I think most items we wanted to finish for 0.8.0 have been merged now. The wheel builds are also all passing on main (including CircleCI) and have been updated for the latest GDAL bugfix release.
The text was updated successfully, but these errors were encountered: