search

European-XFEL / EXtra-data

Access saved EuXFEL data
https://extra-data.rtfd.io
BSD 3-Clause "New" or "Revised" License
7 stars 14 forks source link

Update xarray requirement from <2024.10.0 to <2024.11.0 in /.github/dependabot #568

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Updates the requirements on xarray to permit the latest version.

Release notes

Sourced from xarray's releases.

v2024.10.0

This release brings official support for xarray.DataTree, and compatibility with zarr-python v3!

Aside from these two huge features, it also improves support for vectorised interpolation and fixes various bugs.

Thanks to the 31 contributors to this release: Alfonso Ladino, DWesl, Deepak Cherian, Eni, Etienne Schalk, Holly Mandel, Ilan Gold, Illviljan, Joe Hamman, Justus Magin, Kai Mühlbauer, Karl Krauth, Mark Harfouche, Martey Dodoo, Matt Savoie, Maximilian Roos, Patrick Hoefler, Peter Hill, Renat Sibgatulin, Ryan Abernathey, Spencer Clark, Stephan Hoyer, Tom Augspurger, Tom Nicholas, Vecko, Virgile Andreani, Yvonne Fröhlich, carschandler, joseph nowak, mgunyho and owenlittlejohns

What's Changed

... (truncated)

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
  • 165177e v2024.10.0 release summary (#9678)
  • fbe73ef drop the length from numpy's fixed-width string dtypes (#9586)
  • f24cae3 fixing behaviour for group parameter in open_datatree (#9666)
  • 519f05e Use zarr v3 dimension_names (#9669)
  • 5b2e6f1 fix(zarr): use inplace array.resize for zarr 2 and 3 (#9673)
  • 1f5889a implement dask methods on DataTree (#9670)
  • 521b087 support chunks in open_groups and open_datatree (#9660)
  • b133fdc Compatibility for zarr-python 3.x (#9552)
  • 4798707 Update to_dataframe doc to match current behavior (#9662)
  • 5632c8e Reduce graph size through writing indexes directly into graph for ``map_block...
  • 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)