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.3.0 to <2024.4.0 in /.github/dependabot #508

Closed dependabot[bot] closed 8 months ago

dependabot[bot] commented 8 months ago

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
    This will return a list of all the contributors since the last release: 
    git log "$(git tag --sort=v:refname | tail -1).." --format=%aN | sort -u | perl -pe 's/\n/$1, /'
    This will return the total number of contributors: 
    git log "$(git tag --sort=v:refname | tail -1).." --format=%aN | sort -u | wc -l
  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

... (truncated)

Commits
  • b802607 2024.03.0: Add whats-new (#8891)
  • 47ff159 Add typing to test_groupby.py (#8890)
  • afce18f Avoid in-place multiplication of a large value to an array with small integer...
  • ffb30a8 Check for aligned chunks when writing to existing variables (#8459)
  • 852b7e6 Add dt.date to plottable types (#8873)
  • 5bf2cf4 Optimize writes to existing Zarr stores. (#8875)
  • 2120808 Allow multidimensional variable with same name as dim when constructing datas...
  • cf36559 Don't allow overwriting indexes with region writes (#8877)
  • 473b87f Migrate datatree.py module into xarray.core. (#8789)
  • 55173e8 warn and return bytes undecoded in case of UnicodeDecodeError in h5netcdf-bac...
  • 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)