Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bump the python group across 1 directory with 3 updates #1410

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Bump the python group across 1 directory with 3 updates #1410

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 21, 2025

Updates the requirements on tzdata, xarray and zarr to permit the latest version.
Updates tzdata to 2025.1

Release notes

Sourced from tzdata's releases.

2025.1: Release of upstream tzdata 2025a

Version 2025.1

Upstream version 2025a released 2025-01-15T18:47:24+00:00

Briefly:

Paraguay adopts permanent -03 starting spring 2024. Improve pre-1991 data for the Philippines. Etc/Unknown is now reserved.

Changes to future timestamps

Paraguay will stop changing its clocks after the spring-forward transition on 2024-10-06, so it is now permanently at -03. (Thanks to Heitor David Pinto and Even Scharning.) This affects timestamps starting 2025-03-22, as well as the obsolescent tm_isdst flags starting 2024-10-15.

Changes to past timestamps

Correct timestamps for the Philippines before 1900, and from 1937 through 1990. (Thanks to P Chan for the heads-up and citations.) This includes adjusting local mean time before 1899; fixing transitions in September 1899, January 1937, and June 1954; adding transitions in December 1941, November 1945, March and September 1977, and May and July 1990; and removing incorrect transitions in March and September 1978.

Changes to data

Add zone1970.tab lines for the Concordia and Eyre Bird Observatory research stations. (Thanks to Derick Rethans and Jule Dabars.)

Changes to documentation

The name Etc/Unknown is now reserved: it will not be used by TZDB. This is for compatibility with CLDR, which uses the string "Etc/Unknown" for an unknown or invalid timezone. (Thanks to Justin Grant, Mark Davis, and Guy Harris.)

Cite Internet RFC 9636, which obsoletes RFC 8536 for TZif format.

Changelog

Sourced from tzdata's changelog.

Version 2025.1

Upstream version 2025a released 2025-01-15T18:47:24+00:00

Briefly:

Paraguay adopts permanent -03 starting spring 2024. Improve pre-1991 data for the Philippines. Etc/Unknown is now reserved.

Changes to future timestamps

Paraguay will stop changing its clocks after the spring-forward transition on 2024-10-06, so it is now permanently at -03. (Thanks to Heitor David Pinto and Even Scharning.) This affects timestamps starting 2025-03-22, as well as the obsolescent tm_isdst flags starting 2024-10-15.

Changes to past timestamps

Correct timestamps for the Philippines before 1900, and from 1937 through 1990. (Thanks to P Chan for the heads-up and citations.) This includes adjusting local mean time before 1899; fixing transitions in September 1899, January 1937, and June 1954; adding transitions in December 1941, November 1945, March and September 1977, and May and July 1990; and removing incorrect transitions in March and September 1978.

Changes to data

Add zone1970.tab lines for the Concordia and Eyre Bird Observatory research stations. (Thanks to Derick Rethans and Jule Dabars.)

Changes to documentation

The name Etc/Unknown is now reserved: it will not be used by TZDB. This is for compatibility with CLDR, which uses the string "Etc/Unknown" for an unknown or invalid timezone. (Thanks to Justin Grant, Mark Davis, and Guy Harris.)

Cite Internet RFC 9636, which obsoletes RFC 8536 for TZif format.

Version 2024.2

Upstream version 2024b released 2024-09-04T19:27:47+00:00

Briefly:

Improve historical data for Mexico, Mongolia, and Portugal. System V names are now obsolescent. The main data form now uses %z. The code now conforms to RFC 8536 for early timestamps. Support POSIX.1-2024, which removes asctime_r and ctime_r. Assume POSIX.2-1992 or later for shell scripts. SUPPORT_C89 now defaults to 1.

... (truncated)

Commits
  • 0ccabea Bump release to 2025.1
  • d0078ca Update tzdata to version '2025a'
  • 5bf324b Use proper syntax for multiline env variable
  • a178a14 Fix setup_cfg_fmt pre-commit environment
  • 1397de8 Update pre-commit config
  • 0cce78d Add automatic PR action
  • 3b721cd Don't update the repo unless we need to
  • d913020 Update tzdata to 2024b
  • fdd075c Remove POSIXRULES= from make invocation
  • See full diff in compare view

Updates xarray to 2025.1.1

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.

... (truncated)

Commits

Updates zarr to 3.0.1

Release notes

Sourced from zarr's releases.

v3.0.1

What's Changed

New Contributors

Full Changelog: zarr-developers/zarr-python@v3.0.0...v3.0.1

Changelog

Sourced from zarr's changelog.

3.0.1 (Jan. 17, 2025)

Bug fixes

* Fixes ``order`` argument for Zarr format 2 arrays (:issue:`2679`).

    

  • 

    Fixes a bug that prevented reading Zarr format 2 data with consolidated
    
metadata written using zarr-python version 2 (:issue:2694).
    

    • 

  • 

    Ensure that compressor=None results in no compression when writing Zarr
    
format 2 data (:issue:2708).
    

    • 

  • 

    Fix for empty consolidated metadata dataset: backwards compatibility with
    
Zarr-Python 2 (:issue:2695).
    

    • 



Documentation

  • Add v3.0.0 release announcement banner (:issue:2677).

  • Quickstart guide alignment with V3 API (:issue:2697).

  • Fix doctest failures related to numcodecs 0.15 (:issue:2727).

Other

* Removed some unnecessary files from the source distribution
  to reduce its size. (:issue:`2686`).

    

  • 

    Enable codecov in GitHub actions (:issue:2682).
    

    • 

  • 

    Speed up hypothesis tests (:issue:2650).
    

    • 

  • 

    Remove multiple imports for an import name (:issue:2723).
    

    • 



.. _release_3.0.0:


3.0.0 (Jan. 9, 2025)


3.0.0 is a new major release of Zarr-Python, with many breaking changes.

See the :ref:v3 migration guide for a listing of what's changed.


Normal release note service will resume with further releases in the 3.0.0

series.


Release notes for the zarr-python 2.x and 1.x releases can be found here:

https://zarr.readthedocs.io/en/support-v2/release.html

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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
Bump the python group across 1 directory with 3 updates
bdb5ca8 
Updates the requirements on [tzdata](https://github.com/python/tzdata), [xarray](https://github.com/pydata/xarray) and [zarr](https://github.com/zarr-developers/zarr-python) to permit the latest version.

Updates `tzdata` to 2025.1
- [Release notes](https://github.com/python/tzdata/releases)
- [Changelog](https://github.com/python/tzdata/blob/master/NEWS.md)
- [Commits](python/tzdata@2024.2...2025.1)

Updates `xarray` to 2025.1.1
- [Release notes](https://github.com/pydata/xarray/releases)
- [Changelog](https://github.com/pydata/xarray/blob/main/HOW_TO_RELEASE.md)
- [Commits](pydata/xarray@v2023.01.0...v2025.01.1)

Updates `zarr` to 3.0.1
- [Release notes](https://github.com/zarr-developers/zarr-python/releases)
- [Changelog](https://github.com/zarr-developers/zarr-python/blob/main/docs/release-notes.rst)
- [Commits](zarr-developers/zarr-python@v2.13.0...v3.0.1)

---
updated-dependencies:
- dependency-name: tzdata
  dependency-type: direct:production
  dependency-group: python
- dependency-name: xarray
  dependency-type: direct:production
  dependency-group: python
- dependency-name: zarr
  dependency-type: direct:production
  dependency-group: python
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file python Pull requests that update Python code
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants