Block zarr 3.0.0a1 and 3.0.0a2 in pre-release tests#7217
Conversation
|
@napari-bot update constraints |
|
Updated packages: This workflow cannot automatically update your PR or create PR to your repository. But you could open such PR by clicking the link: Czaki/napari@block_zarr_3.0.0a1...napari-bot:auto-update-dependencies/Czaki/napari/block_zarr_3.0.0a1. You could also get the updated files from the https://github.com/napari-bot/napari/tree/auto-update-dependencies/Czaki/napari/block_zarr_3.0.0a1/resources/constraints. Or ask the maintainers to provide you the contents of the constraints artifact from the run https://github.com/napari/napari/actions/runs/10567195732 |
|
Pydantic 2.9.0b1 now crashing the tests... |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7217 +/- ##
==========================================
- Coverage 92.83% 92.73% -0.11%
==========================================
Files 623 623
Lines 57044 57044
==========================================
- Hits 52957 52899 -58
- Misses 4087 4145 +58 ☔ View full report in Codecov by Sentry. |
|
Will you also block pydantic @Czaki? |
The pydantic 2.9.0b2 solves the reported bug and I do not want to block 2.9.0b1 because of this bug astral-sh/uv#6640 |
References and relevant issues
closes #7193
Description
When try to fix zarr problems with zarr 3.0.0 in #7215 I have found that it is not easy with this release, so I prefer to block 3.0.0a1 release and open issue in zarr