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 0.12 #2603
Comments
I am planning to do a release tomorrow. Are there specific PRs that are more or less ready you would prefer to see included? |
Ah, and #2596 to get rid of matplotlib warnings. |
Seems like CI failures on main might need to be resolved first - fiona doesn't appear to import correctly: https://github.com/geopandas/geopandas/actions/runs/3300337184/jobs/5444725744 Looking at the latest commits, we seem to have had successful builds with fiona 1.8.22 when #2575 was merged, but the latest commit seems to install it then show fiona =None in |
The CI issues are an upstream conda-forge pinning issue (in tiledb, which is one of the dependencies of GDAL), so not our concern directly, but of course we want green CI before releasing to verify our own tests are passing. I am trying to temporary fix with pinning to an older version in #2609 |
Released! -> https://github.com/geopandas/geopandas/releases/tag/v0.12.0 (https://pypi.org/project/geopandas/0.12.0/) Will announce if conda-forge is ready |
Thank you @jorisvandenbossche! |
In Now that #2275 has been merged, do we still need this constraint? |
Oh no, I forgot about that .. Yes, that should have been removed. I suppose I will do a 0.12.1 with that then. |
v0.12.1 with the pin removed is released! |
Thanks @jorisvandenbossche ! Now able to install Shapely 2.0b2 alongside GeoPandas 0.12.1 without difficulty via Poetry. |
Release and the follow-up patch are out. Closing. |
I was thinking to release a 0.12.2 including #2641, so we have a release fixing the known compat issues with shapely (with shapely 2.0 final being released in a few days) Since we haven't yet merged new features since 0.12.1, we could actually just release from the main branch. However, I am a bit weary about #2512 (which could have some side effects on packaging) being included in a bug-fix release, so I could also make a branch. |
Fine with me! We can do a branch if you think #2512 could cause issues. I haven't seen them in a wild but that Debian packaging (or which was that) may not be as smooth. Not sure how adapted they are at this point. |
0.12.2 is out. |
I can do the feedstock update (to not have to wait on the bot) |
We discussed this in one of the previous community meetings to do a 0.12 release to have a GeoPandas release that works together with Shapely 2.0:
Shapely 2.0 beta 1 was released yesterday, so maybe we should also try to release GeoPandas 0.12 shortly. This will make it much easier for people to actually test shapely 2.0 in environments where they also use geopandas (without having to install the dev version of geopandas).
We also have the following in the meeting notes:
This is something we still need to do. #2275 kept pygeos as the default engine if installed. So for people that also install shapely 2.0b1 in an env with pygeos, they have to set an environment variable to actually test shapely.
The text was updated successfully, but these errors were encountered: