Skip to content

Bump the package-updates group across 1 directory with 12 updates - #113

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/package-updates-074ae4f678
Open

Bump the package-updates group across 1 directory with 12 updates#113
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/package-updates-074ae4f678

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 30, 2026

Copy link
Copy Markdown
Contributor

Bumps the package-updates group with 12 updates in the / directory:

Package From To
pydantic 2.13.3 2.13.4
zarr 3.1.6 3.2.1
numpy 2.4.4 2.5.0
dask 2026.3.0 2026.6.0
coverage 7.13.5 7.14.3
pytest 9.0.3 9.1.1
ruff 0.15.12 0.15.20
mypy 1.20.2 2.1.0
types-pyyaml 6.0.12.20260408 6.0.12.20260518
types-shapely 2.1.0.20260408 2.1.0.20260630
atheris 3.0.0 3.1.0
zensical 0.0.37 0.0.46

Updates pydantic from 2.13.3 to 2.13.4

Release notes

Sourced from pydantic's releases.

v2.13.4 2026-05-06

v2.13.4 (2026-05-06)

What's Changed

Packaging

Fixes

Full Changelog: pydantic/pydantic@v2.13.3...v2.13.4

Changelog

Sourced from pydantic's changelog.

v2.13.4 (2026-05-06)

GitHub release

What's Changed

Packaging

Fixes

Commits
  • cf67d4b Fix linting
  • f0d8a21 Prepare release v2.13.4
  • 5e3fe1d Check for pydantic tag pattern in CI
  • 7f9edcc Document tagging conventions
  • b46a0c9 Adapt pydantic-core linker flags on macOS
  • 50629c8 Update to PyPy 7.3.22
  • 8522ebb Preserve RootModel core metadata
  • a37f3af Adapt MISSING sentinel test to work with unreleased typing_extensions ver...
  • 909259a Remove Logfire example in documentation
  • 2c4174c Bump libc from 0.2.155 to 0.2.185
  • See full diff in compare view

Updates zarr from 3.1.6 to 3.2.1

Release notes

Sourced from zarr's releases.

v3.2.1

What's Changed

Full Changelog: zarr-developers/zarr-python@v3.2.0...v3.2.1

v3.2.0

What's Changed

... (truncated)

Changelog

Sourced from zarr's changelog.

3.2.1 (2026-05-05)

Bugfixes

  • Fixed a CastValue validation bug where the "can we use an out-of-range mode" check inspected the source dtype instead of the target dtype. This meant arrays with a float source dtype and an integer target dtype incorrectly raised a ValueError when configured with a wrap out-of-range mode. (#3938)
  • Fixed a bug where the codec pipeline evolved each codec against the original array spec instead of the spec produced by upstream array-to-array codecs. This caused failures whenever an upstream codec changed the dtype between codec boundaries — e.g. arrays using CastValue to convert a single-byte source dtype (int8) to a multi-byte target dtype (int16) raised a ValueError from BytesCodec about a missing endian configuration. (#3941)
  • Fixed breakage in existing fsspec-dependent workflows caused by associating the "memory" URL scheme with instances of ManagedMemoryStore instead of fsspec's memory-backed store. After this change, store URLs with a "memory" scheme are handled differently when fsspec is installed: with fsspec, a FsspecStore backed by a MemoryFileSystem is used. Without fsspec, a ManagedMemoryStore is used. (#3944)

3.2.0 (2026-04-30)

Features

  • Adds a new in-memory storage backend called ManagedMemoryStore. Instances of ManagedMemoryStore function similarly to MemoryStore, but instances of ManagedMemoryStore can be constructed from a URL like memory://store. (#3679)

  • Added array.read_missing_chunks configuration option. When set to False, reading missing chunks raises a ChunkNotFoundError instead of filling them with the array's fill value. (#3748)

  • Added Struct class (subclass of Structured) implementing the zarr-extensions struct dtype spec. Uses object-style field format and dict fill values. Legacy Structured remains available for backward compatibility. (#3781)

  • Add support for rectilinear (variable-sized) chunk grids. This feature is experimental and must be explicitly enabled via zarr.config.set({'array.rectilinear_chunks': True}).

    Rectilinear chunks can be used through:

    • Creating arrays: Pass nested sequences (e.g., [[10, 20, 30], [50, 50]]) to chunks in zarr.create_array, zarr.from_array, zarr.zeros, zarr.ones, zarr.full, zarr.open, and related functions, or to chunk_shape in zarr.create.
    • Opening existing arrays: Arrays stored with the rectilinear chunk grid are read transparently via zarr.open and zarr.open_array.
    • Rectilinear sharding: Shard boundaries can be rectilinear while inner chunks remain regular.

    Breaking change: The validate method on BaseCodec and CodecPipeline now receives a ChunkGridMetadata instance instead of a ChunkGrid instance for the chunk_grid parameter. Third-party codecs that override validate and inspect the chunk grid will need to update their type annotations. No known downstream packages were using this parameter. (#3802)

  • Add cast_value and scale_offset codecs. (#3874)

Bugfixes

  • Fix SyncError raised when assigning a zarr.Array as the value in a __setitem__ call (e.g. dst[:] = src where src is a zarr array). The source array is now converted to a NumPy array before entering the async codec pipeline. (#3611)

... (truncated)

Commits
  • 85890b3 release : 3.2.1 release notes (#3942)
  • 37ae37b fix: defer to fsspec for memory url scheme (#3944)
  • 021662c fix: use contextual arrayspec when validating / evolving codecs (#3941)
  • ad374b5 cast_value data type validation was checking the source data type instead of ...
  • f8c0c5d feat:metadata package (#3919)
  • 3ede5e8 docs: build 3.2.0 release notes (#3932)
  • 870fabd chore/3.2.0 release notes (#3927)
  • ac667c1 chore: automate more of the release process (#3896)
  • 23e9635 feat: add cast_value and scale_offset codecs (#3874)
  • 279d400 fix(storage): preserve leading slashes in FsspecStore.path (#3926)
  • Additional commits viewable in compare view

Updates numpy from 2.4.4 to 2.5.0

Release notes

Sourced from numpy's releases.

v2.5.0 (June 21, 2026)

NumPy 2.5.0 Release Notes

Numpy 2.5.0 is a transitional release. It drops support for Python 3.11, marking the end of distutils, and expires a large number of deprecations made in the 2.0.x release. It also improves free threading and brings sorting into compliance with the array-api standard with the addition of descending sorts. There is also a fair amount of preparation for Python 3.15, which will be supported starting with the first rc.

This release supports Python versions 3.12-3.14.

Highlights

  • Distutils has been removed,
  • Many expired deprecations, see below,
  • Many new deprecations, see below,
  • Many static typing improvements.
  • Improved support for free threading,
  • Support for descending sorts,

See New Features below for other additions.

Deprecations

  • numpy.char.chararray is deprecated. Use an ndarray with a string or bytes dtype instead.

    (gh-30605)

  • numpy.take now correctly checks if the result can be cast to the provided out=out under the same-kind rule. A DeprecationWarning is given now when this check fails. Previously, take incorrectly checked if out could be cast to the result (the wrong direction). This deprecation also affects compress and possibly other functions. (Future versions of NumPy may tighten the casting check further.)

    (gh-30615)

  • The numpy.char.[as]array functions are deprecated. Use an numpy.[as]array with a string or bytes dtype instead.

    (gh-30802)

  • Setting the dtype attribute is deprecated because mutating an array is unsafe if an array is shared, especially by multiple threads. As an alternative, you can create a view with a new dtype via array.view(dtype=new_dtype).

    (gh-29244)

... (truncated)

Changelog

Sourced from numpy's changelog.

This is a walkthrough of the NumPy 2.4.0 release on Linux, which will be the first feature release using the numpy/numpy-release <https://github.com/numpy/numpy-release>__ repository.

The commands can be copied into the command line, but be sure to replace 2.4.0 with the correct version. This should be read together with the :ref:general release guide <prepare_release>.

Facility preparation

Before beginning to make a release, use the requirements/*_requirements.txt files to ensure that you have the needed software. Most software can be installed with pip, but some will require apt-get, dnf, or whatever your system uses for software. You will also need a GitHub personal access token (PAT) to push the documentation. There are a few ways to streamline things:

  • Git can be set up to use a keyring to store your GitHub personal access token. Search online for the details.

Prior to release

Add/drop Python versions

When adding or dropping Python versions, multiple config and CI files need to be edited in addition to changing the minimum version in pyproject.toml. Make these changes in an ordinary PR against main and backport if necessary. We currently release wheels for new Python versions after the first Python RC once manylinux and cibuildwheel support that new Python version.

Backport pull requests

Changes that have been marked for this release must be backported to the maintenance/2.4.x branch.

Update 2.4.0 milestones

Look at the issues/prs with 2.4.0 milestones and either push them off to a later version, or maybe remove the milestone. You may need to add a milestone.

Check the numpy-release repo

... (truncated)

Commits
  • 6910b28 Merge pull request #31706 from charris/prepare-2.5.0-release
  • e0acd2b REL: Prepare for the NumPy 2.5.0 release.
  • 8d928b7 Merge pull request #31704 from charris/backport-31649
  • c2055ba MAINT: update openblas to 0.3.33.112.0 (#31649)
  • ce17c81 Merge pull request #31703 from charris/backport-31609
  • 3de6203 BUG: fix StringDType distinct-allocator bugs and add tests (#31609)
  • c723971 Merge pull request #31700 from charris/backport-31694
  • 64513b2 MAINT: Bump pypa/cibuildwheel from 3.4.1 to 4.1.0
  • 04707f0 Merge pull request #31698 from charris/try-fix-emscripten
  • 5cf0686 MAINT: Try to fix emscripten wheel build.
  • Additional commits viewable in compare view

Updates dask from 2026.3.0 to 2026.6.0

Release notes

Sourced from dask's releases.

2026.6.0

Changes

... (truncated)

Changelog

Sourced from dask's changelog.

There are a variety of other projects related to dask that are often co-released. We may want to check their status while releasing

Releasing dask and distributed:

  • Check the release issue on https://github.com/dask/community to see if there are any remaining blockers. If not, comment on the issue signalling that you are starting the release

  • Update release notes in docs/source/changelog.rst Start by using this script to autogenerate some of the changelog entries:

    git log $(git describe --tags --abbrev=0)..HEAD --pretty=format:"- %s \`%an\`_"  > change.md && sed -i -e 's/(#/(:pr:`/g' change.md && sed -i -e 's/) `/`) `/g' change.md
    

    Replace single backticks with double backticks.

    Sort the entries into subsections and render docs (make html) to make sure that the changelog renders properly. In particular watch warnings for new contributors who don't yet have a github link at the end of the file.

    Add any new contributors' github links to the end of the file (gh pr view --json author <PR> is helpful for getting their usernames).

  • Update dependency bounds in all pyproject.toml files

    • In dask/pyproject.toml, set the optional Distributed extra. For example, for a 2026.6.0 release:

      [project.optional-dependencies]
      distributed = ["distributed >=2026.6.0,<2026.6.1"]
      
    • In distributed/pyproject.toml, set the required Dask dependency. For example, for a 2026.6.0 release:

      dependencies = [
          "dask >=2026.6.0,<2026.6.1",
          ...
      ]
      
    • pins should be >= the current version but < the next version to allow for development installs to resolve correctly

    Dask can be released while its optional distributed extra points at the not-yet-published matching Distributed release. Distributed cannot be published before the matching Dask release is available, because Dask is a required dependency.

  • Commit

    git commit -a -m "Version YYYY.M.X"
    

... (truncated)

Commits
  • f973ad8 Version 2026.6.0
  • aea7965 Add PyPI release workflow (#12452)
  • c437b7a Pandas 3.1: The inplace keyword in DataFrame.drop is deprecated (#12447)
  • 99af142 test_concat_categorical is still flaky on Pandas 2.0 (#12454)
  • 2be4507 Add tests for the array assert_eq helper (#12441)
  • d0666ee Revert "security: enable Jinja2 autoescape to prevent XSS in HTML rep… (#12451)
  • e2cdbb0 Bump codecov/codecov-action from 6 to 7 (#12450)
  • f8e1de3 fix:Dataframe.merge loses data when there are 128 or 129 partitions (#12430)
  • 9124454 security: enable Jinja2 autoescape to prevent XSS in HTML reprs (#12423)
  • a0856a0 Test vs. NumPy 1.26 and PyArrow 18 (#12445)
  • Additional commits viewable in compare view

Updates coverage from 7.13.5 to 7.14.3

Changelog

Sourced from coverage's changelog.

Version 7.14.3 — 2026-06-22

  • Fix: the default ... exclusion rule now also matches function bodies whose closing return-type bracket is on its own line (for example, after a long -> dict[ ... ] annotation that a formatter has split over multiple lines). Closes issue 2185, thanks Mengjia Shang <pull 2196_>.

  • Fix: On 3.13t, we incorrectly issued Couldn't import C tracer errors. We can't import the C tracer because in 7.14.2 we stopped shipping compiled wheels for 3.13t. Thanks, Hugo van Kemenade <pull 2203_>_.

.. _issue 2185: coveragepy/coveragepy#2185 .. _pull 2196: coveragepy/coveragepy#2196 .. _pull 2203: coveragepy/coveragepy#2203

.. _changes_7-14-2:

Version 7.14.2 — 2026-06-20

  • Fix: some messages were being written to stdout, making coverage json -o - useless for capturing JSON output. Now messages are written to stderr, fixing issue 2197_.

  • Fix: CoverageData kept one SQLite connection per thread that recorded coverage, but never closed them when those threads terminated. On long runs with many short-lived threads this leaked one file descriptor per dead thread, eventually failing with OSError: [Errno 24] Too many open files. Connections belonging to terminated threads are now closed and dropped. Fixes issue 2192. Thanks, Matthew Lloyd <pull 2193_>.

  • Fix: when using sys.monitoring, we were assuming we could use the COVERAGE_ID tool id. But other tools might also assume they could use that id. Pre-allocated ids don't really make sense, so now we search for a usable one instead. Fixes issue 2187_.

  • Following the advice of cibuildwheel <no-13t_>_, we no longer distribute wheels for Python 3.13 free-threaded.

.. _issue 2187: coveragepy/coveragepy#2187 .. _issue 2192: coveragepy/coveragepy#2192 .. _pull 2193: coveragepy/coveragepy#2193 .. _issue 2197: coveragepy/coveragepy#2197 .. _no-13t: https://py-free-threading.github.io/ci/#building-free-threaded-wheels-with-cibuildwheel

.. _changes_7-14-1:

... (truncated)

Commits
  • 22f13ea docs: sample HTML for 7.14.3
  • 2ca4e5f docs: prep for 7.14.3
  • 01d714e docs: add changelog entry for #2203
  • f36248d fix: don't emit 'Couldn't import C tracer' warning for 3.13t (#2203)
  • 86d73d1 docs: thanks, Mengjia Shang
  • 3d4ae3c docs: add the #2196 pr link to CHANGES
  • f4b2b4d fix: exclude ... bodies after multi-line return-type annotations (#2185) (#...
  • 1980ed0 chore: bump sigstore/gh-action-sigstore-python (#2201)
  • bca3217 build: since we don't ship 3.13t, don't test it
  • 77550d8 docs: oops, mismatched pull requests
  • Additional commits viewable in compare view

Updates pytest from 9.0.3 to 9.1.1

Release notes

Sourced from pytest's releases.

9.1.1

pytest 9.1.1 (2026-06-19)

Bug fixes

  • #14220: Fixed a logic bug in pytest.RaisesGroup which would might cause it to display incorrect "It matches FooError() which was paired with BarError" messages.
  • #14591: Fixed a regression in pytest 9.1.0 which caused overriding a parametrized fixture with an indirect @​pytest.mark.parametrize to fail with "duplicate parametrization of '<fixture name>'".
  • #14606: Fixed list-item typing errors from mypy in @pytest.mark.parametrize <pytest.mark.parametrize ref> argvalues parameter.
  • #14608: Fixed a regression in pytest 9.1.0 where conftest.py files located in <invocation dir>/test* were no longer loaded as initial conftests when invoked without arguments. This could cause certain hooks (like pytest_addoption) in these files to not fire.

9.1.0

pytest 9.1.0 (2026-06-13)

Removals and backward incompatible breaking changes

  • #14533: When using --doctest-modules, autouse fixtures with module, package or session scope that are defined inline in Python test modules (not plugins or conftests) will now possibly execute twice.

    If this is undesirable, move the fixture definition to a conftest.py file if possible.

    Technical explanation for those interested: When using --doctest-modules, pytest possibly collects Python modules twice, once as pytest.Module and once as a DoctestModule (depending on the configuration). Due to improvements in pytest's fixture implementation, if e.g. the DoctestModule collects a fixture, it is now visible to it only, and not to the Module. This means that both need to register the fixtures independently.

Deprecations (removal in next major release)

  • #10819: Added a deprecation warning for class-scoped fixtures defined as instance methods (without @classmethod). Such fixtures set attributes on a different instance than the test methods use, leading to unexpected behavior. Use @classmethod decorator instead -- by yastcher.

    See 10819 and 14011.

  • #12882: Calling request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue> during teardown to request a fixture that was not already requested is now deprecated and will become an error in pytest 10.

    See dynamic-fixture-request-during-teardown for details.

  • #13409: Using non-~collections.abc.Collection iterables (such as generators, iterators, or custom iterable objects) for the argvalues parameter in @pytest.mark.parametrize <pytest.mark.parametrize ref> and metafunc.parametrize <pytest.Metafunc.parametrize> is now deprecated.

    These iterables get exhausted after the first iteration, leading to tests getting unexpectedly skipped in cases such as running pytest.main() multiple times, using class-level parametrize decorators, or collecting tests multiple times.

    See parametrize-iterators for details and suggestions.

  • #13946: The private config.inicfg attribute is now deprecated. Use config.getini() <pytest.Config.getini> to access configuration values instead.

    See config-inicfg for more details.

  • #14004: Passing baseid to ~pytest.FixtureDef or nodeid strings to fixture registration APIs is now deprecated. These are internal pytest APIs that are used by some plugins.

... (truncated)

Commits
  • cf470ec Prepare release version 9.1.1
  • e0c8ce6 Merge pull request #14625 from pytest-dev/patchback/backports/9.1.x/a07c31a97...
  • 1b82d16 Merge pull request #14624 from pytest-dev/patchback/backports/9.1.x/b375b79ec...
  • 501c4bc Merge pull request #14596 from bluetech/doc-classmethod
  • b61f588 Merge pull request #14622 from chrisburr/fix-14608-initial-conftest-test-subdir
  • 9a567e0 [automated] Update plugin list (#14617) (#14618)
  • ef8b299 Merge pull request #14620 from pytest-dev/patchback/backports/9.1.x/680f9f3ed...
  • 66abd07 Merge pull request #14220 from bysiber/fix-stale-iexp-raisesgroup
  • 79fbf93 Merge pull request #14612 from pytest-dev/patchback/backports/9.1.x/974ed48b6...
  • 0d312eb Merge pull request #14611 from bluetech/parametrize-argvalues-typing
  • Additional commits viewable in compare view

Updates ruff from 0.15.12 to 0.15.20

Release notes

Sourced from ruff's releases.

0.15.20

Release Notes

Released on 2026-06-25.

Preview features

  • Allow human-readable names in rule selectors (#25887)
  • Emit a warning instead of an error for unknown rule selectors (#26113)
  • Match noqa shebang handling in ruff:ignore comments (#26286)
  • [ruff] Remove pytest-fixture-autouse (RUF076) (#26240, #26371)

Documentation

  • Add versioning sections to custom crate READMEs (#26317)
  • Update ruff_python_parser README for crates.io (#26315)
  • [perflint] Clarify that PERF402 applies to any iterable (#26242)

Contributors

Install ruff 0.15.20

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://releases.astral.sh/github/ruff/releases/download/0.15.20/ruff-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://releases.astral.sh/github/ruff/releases/download/0.15.20/ruff-installer.ps1 | iex"

Download ruff 0.15.20

File Platform Checksum
ruff-aarch64-apple-darwin.tar.gz Apple Silicon macOS checksum
ruff-x86_64-apple-darwin.tar.gz Intel macOS checksum
ruff-aarch64-pc-windows-msvc.zip ARM64 Windows checksum
ruff-i686-pc-windows-msvc.zip x86 Windows checksum
ruff-x86_64-pc-windows-msvc.zip x64 Windows checksum
ruff-aarch64-unknown-linux-gnu.tar.gz ARM64 Linux checksum
ruff-i686-unknown-linux-gnu.tar.gz x86 Linux checksum

... (truncated)

Changelog

Sourced from ruff's changelog.

0.15.20

Released on 2026-06-25.

Preview features

  • Allow human-readable names in rule selectors (#25887)
  • Emit a warning instead of an error for unknown rule selectors (#26113)
  • Match noqa shebang handling in ruff:ignore comments (#26286)
  • [ruff] Remove pytest-fixture-autouse (RUF076) (#26240, #26371)

Documentation

  • Add versioning sections to custom crate READMEs (

Bumps the package-updates group with 12 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [pydantic](https://github.com/pydantic/pydantic) | `2.13.3` | `2.13.4` |
| [zarr](https://github.com/zarr-developers/zarr-python) | `3.1.6` | `3.2.1` |
| [numpy](https://github.com/numpy/numpy) | `2.4.4` | `2.5.0` |
| [dask](https://github.com/dask/dask) | `2026.3.0` | `2026.6.0` |
| [coverage](https://github.com/coveragepy/coveragepy) | `7.13.5` | `7.14.3` |
| [pytest](https://github.com/pytest-dev/pytest) | `9.0.3` | `9.1.1` |
| [ruff](https://github.com/astral-sh/ruff) | `0.15.12` | `0.15.20` |
| [mypy](https://github.com/python/mypy) | `1.20.2` | `2.1.0` |
| [types-pyyaml](https://github.com/python/typeshed) | `6.0.12.20260408` | `6.0.12.20260518` |
| [types-shapely](https://github.com/python/typeshed) | `2.1.0.20260408` | `2.1.0.20260630` |
| [atheris](https://github.com/google/atheris) | `3.0.0` | `3.1.0` |
| [zensical](https://github.com/zensical/zensical) | `0.0.37` | `0.0.46` |



Updates `pydantic` from 2.13.3 to 2.13.4
- [Release notes](https://github.com/pydantic/pydantic/releases)
- [Changelog](https://github.com/pydantic/pydantic/blob/main/HISTORY.md)
- [Commits](pydantic/pydantic@v2.13.3...v2.13.4)

Updates `zarr` from 3.1.6 to 3.2.1
- [Release notes](https://github.com/zarr-developers/zarr-python/releases)
- [Changelog](https://github.com/zarr-developers/zarr-python/blob/main/docs/release-notes.md)
- [Commits](zarr-developers/zarr-python@v3.1.6...v3.2.1)

Updates `numpy` from 2.4.4 to 2.5.0
- [Release notes](https://github.com/numpy/numpy/releases)
- [Changelog](https://github.com/numpy/numpy/blob/main/doc/RELEASE_WALKTHROUGH.rst)
- [Commits](numpy/numpy@v2.4.4...v2.5.0)

Updates `dask` from 2026.3.0 to 2026.6.0
- [Release notes](https://github.com/dask/dask/releases)
- [Changelog](https://github.com/dask/dask/blob/main/docs/release-procedure.md)
- [Commits](dask/dask@2026.3.0...2026.6.0)

Updates `coverage` from 7.13.5 to 7.14.3
- [Release notes](https://github.com/coveragepy/coveragepy/releases)
- [Changelog](https://github.com/coveragepy/coveragepy/blob/main/CHANGES.rst)
- [Commits](coveragepy/coveragepy@7.13.5...7.14.3)

Updates `pytest` from 9.0.3 to 9.1.1
- [Release notes](https://github.com/pytest-dev/pytest/releases)
- [Changelog](https://github.com/pytest-dev/pytest/blob/main/CHANGELOG.rst)
- [Commits](pytest-dev/pytest@9.0.3...9.1.1)

Updates `ruff` from 0.15.12 to 0.15.20
- [Release notes](https://github.com/astral-sh/ruff/releases)
- [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md)
- [Commits](astral-sh/ruff@0.15.12...0.15.20)

Updates `mypy` from 1.20.2 to 2.1.0
- [Changelog](https://github.com/python/mypy/blob/master/CHANGELOG.md)
- [Commits](python/mypy@v1.20.2...v2.1.0)

Updates `types-pyyaml` from 6.0.12.20260408 to 6.0.12.20260518
- [Commits](https://github.com/python/typeshed/commits)

Updates `types-shapely` from 2.1.0.20260408 to 2.1.0.20260630
- [Commits](https://github.com/python/typeshed/commits)

Updates `atheris` from 3.0.0 to 3.1.0
- [Commits](https://github.com/google/atheris/commits)

Updates `zensical` from 0.0.37 to 0.0.46
- [Release notes](https://github.com/zensical/zensical/releases)
- [Commits](zensical/zensical@v0.0.37...v0.0.46)

---
updated-dependencies:
- dependency-name: pydantic
  dependency-version: 2.13.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: package-updates
- dependency-name: zarr
  dependency-version: 3.2.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: package-updates
- dependency-name: numpy
  dependency-version: 2.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: package-updates
- dependency-name: dask
  dependency-version: 2026.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: package-updates
- dependency-name: coverage
  dependency-version: 7.14.3
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: package-updates
- dependency-name: pytest
  dependency-version: 9.1.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: package-updates
- dependency-name: ruff
  dependency-version: 0.15.20
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: package-updates
- dependency-name: mypy
  dependency-version: 2.1.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: package-updates
- dependency-name: types-pyyaml
  dependency-version: 6.0.12.20260518
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: package-updates
- dependency-name: types-shapely
  dependency-version: 2.1.0.20260630
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: package-updates
- dependency-name: atheris
  dependency-version: 3.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: package-updates
- dependency-name: zensical
  dependency-version: 0.0.46
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: package-updates
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency major Concerns a bug with major severity python Pull requests that update python code labels Jun 30, 2026
@dependabot @github

dependabot Bot commented on behalf of github Jul 7, 2026

Copy link
Copy Markdown
Contributor Author

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot recreate.

3 similar comments
@dependabot @github

dependabot Bot commented on behalf of github Jul 14, 2026

Copy link
Copy Markdown
Contributor Author

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot recreate.

@dependabot @github

dependabot Bot commented on behalf of github Jul 21, 2026

Copy link
Copy Markdown
Contributor Author

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot recreate.

@dependabot @github

dependabot Bot commented on behalf of github Jul 28, 2026

Copy link
Copy Markdown
Contributor Author

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot recreate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency major Concerns a bug with major severity python Pull requests that update python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants