Update xarray requirement from <2024.8.0 to <2024.10.0 in /.github/dependabot

[dependabot[bot]]

Updates the requirements on xarray to permit the latest version.

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.

6. After merging, again ensure your main branch is synced to upstream:

   git pull upstream main
   

7. If you have any doubts, run the full test suite one final time!

... (truncated)

Commits

• ed0418b Release notes for v2024.09.0 (#9480)
• 781877c Fix DataTree.coords.__setitem__ by adding DataTreeCoordinates class (#9451)
• fac2c89 Rename DataTree's "ds" and "data" to "dataset" (#9476)
• a6bacfe Update DataTree repr to indicate inheritance (#9470)
• 9735216 Bump pypa/gh-action-pypi-publish in the actions group (#9460)
• 6baceca Repo checker (#9450)
• cc74d3a Add days_in_year and decimal_year to dt accessor (#9105)
• cea354f remove parent argument from DataTree.init (#9465)
• 40666b2 Fix inheritance in DataTree.copy() (#9457)
• 45a0027 Implement DataTree.__delitem__ (#9453)
• 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 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)