Update h5py requirement from <3.13.0,>=3.1.0 to >=3.1.0,<3.15.0 in /tests

[dependabot]

Updates the requirements on h5py to permit the latest version.

Changelog

Sourced from h5py's changelog.

.. _release_guide:

Release Guide

Steps to make an h5py release:

1. Have a look for any open issues or PRs which we might want to solve/merge before the release.

2. Prepare a new branch, e.g. git switch -c prepare-3.14

3. Prepare the release notes. The goal is to describe changes visible to users & repackagers of h5py in a form that doesn't assume 'internal' development knowledge. If something breaks, or behaviour changes unexpectedly, the release notes should let someone make a good guess which change is involved.

   • Check for recent merged PRs with no milestone <https://github.com/h5py/h5py/pulls?q=is%3Amerged+is%3Apr+no%3Amilestone>_, and assign them to the current release milestone. We can ignore PRs which only touch CI with no consequences for users.
   • Go to the milestone page. If there are open issues/PRs there, decide whether to include or defer them.
   • Assemble the release notes in docs/whatsnew based on the list of merged PRs. Commit the changes.

4. Update the version number & commit the changes. The files that need changing are:

   • setup.py
   • h5py/version.py
   • docs/conf.py

5. Push the branch, open a PR, wait for the CI. Check the RTD build for the newly added release notes (formatting & cross-links). Optionally, wait for other maintainers to check it as well.

6. When everything looks good, merge the PR.

7. Checkout the master branch, pull, make and push the tag, which will cause CI to build wheels & make a GitHub release::

   git switch master git pull git tag 3.14.0 # <-- change this git push --tags

8. Prepare the sdist::

   git clean -xfdi python -m build --sdist

9. Download the wheels: gh release download 3.14.0 -D dist/

10. Upload to PyPI: twine upload dist/h5py-3.14.0* - this requires a token from PyPI, which must be supplied to twine <https://twine.readthedocs.io/en/stable/#configuration>_.

... (truncated)

Commits

• 07a5511 Merge pull request #2591 from takluyver/prepare-3.14
• a70e013 Add versionadded box for numpy strings support
• 6186edf Version number -> 3.14.0
• a9e2d46 Add release notes for 3.14
• ab19424 Merge pull request #2585 from ArvidJB/fork_thread_phil
• 60c5cd9 Merge pull request #2590 from neutrinoceros/tst/bump-windows-image
• e3cc528 MNT: bump windows image on azure (2019 -> 2022)
• a51de9f Time out tests on deadlock instead of hanging and leaving zombie processes be...
• 7c14cd9 Merge pull request #2586 from takluyver/h5d-write-chunk
• a92ab7c Address review comments
• 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)

[dependabot]

Assignees

The following users could not be added as assignees: akuporos, p-wysocki, rkazants. Either they do not exist or they do not have the correct permissions to be added as an assignee.

Please fix the above issues or remove invalid values from dependabot.yml.