Update xarray requirement from <2025.10.0 to <2025.11.0 in /.github/dependabot

[dependabot]

Updates the requirements on xarray to permit the latest version.

Release notes

Sourced from xarray's releases.

v2025.10.0

This release reverts a breaking change to Xarray's preferred netCDF backend.

Changelog

Sourced from xarray's changelog.

How to issue an xarray release in 16 easy steps

Time required: about an hour.

These instructions assume that upstream refers to the main repository:

$ git remote -v
{...}
upstream        https://github.com/pydata/xarray (fetch)
upstream        https://github.com/pydata/xarray (push)

1. Ensure your main branch is synced to upstream:

   git switch main
   git pull upstream main

2. Add a list of contributors. First fetch all previous release tags so we can see the version number of the last release was:

   git fetch upstream --tags

   Then run

   python ci/release_contributors.py

   (needs gitpython and toolz / cytoolz)

   and copy the output.

3. Write a release summary: ~50 words describing the high level features. This will be used in the release emails, tweets, GitHub release notes, etc.

4. Look over whats-new.rst and the docs. Make sure "What's New" is complete (check the date!) and add the release summary at the top. Things to watch out for:

   • Important new features should be highlighted towards the top.
   • Function/method references should include links to the API docs.
   • Sometimes notes get added in the wrong section of whats-new, typically due to a bad merge. Check for these before a release by using git diff, e.g., git diff v{YYYY.MM.X-1} whats-new.rst where {YYYY.MM.X-1} is the previous release.

5. Open a PR with the release summary and whatsnew changes; in particular the release headline should get feedback from the team on what's important to include.

... (truncated)

Commits

• f880049 release notes for 2025.10.0 (#10821)
• 6aa48c3 Switch back default netCDF engine (#10817)
• a440558 Fix error when writing scalar varaibles to Zarr with region={} (#10796)
• 4466deb Enable htmlzip documentation build (#10815)
• 57d3191 allow ignoring contributors by email for the release notes (#10814)
• badb6f1 Add supports_groups=True to Zarr backend (#10809)
• eed12c4 New blank whats-new section (#10798)
• 3fa5598 Release notes for 2025.09.1 (#10797)
• aff76cf Less vertical whitespace in HTML reprs (#10795)
• cbe04e6 Use a default fill_value of NaN for floats in Zarr v3 (#10757)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)