search

European-XFEL / EXtra-geom

Use EuXFEL detector geometry to assemble images
https://extra-geom.rtfd.io
BSD 3-Clause "New" or "Revised" License
5 stars 4 forks source link

Update xarray requirement from <2023.11.0 to <2023.12.0 in /.github/dependabot #259

Closed dependabot[bot] closed 11 months ago

dependabot[bot] commented 11 months ago

Updates the requirements on xarray to permit the latest version.

Release notes

Sourced from xarray's releases.

v2023.11.0

[!NOTE] This is our 10th year anniversary release! Thank you for your love and support.

This release brings the ability to use opt_einsum for :py:func:xarray.dot by default, support for auto-detecting region when writing partial datasets to Zarr, and the use of h5py drivers with h5netcdf.

Thanks to the 19 contributors to this release: Aman Bagrecha, Anderson Banihirwe, Ben Mares, Deepak Cherian, Dimitri Papadopoulos Orfanos, Ezequiel Cimadevilla Alvarez, Illviljan, Justus Magin, Katelyn FitzGerald, Kai Muehlbauer, Martin Durant, Maximilian Roos, Metamess, Sam Levang, Spencer Clark, Tom Nicholas, mgunyho, templiert

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
    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


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)