Skip to content

MAINT: Update packaging requirement from >=24.0 to >=26.2 in /.github/constraints - #102

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/dot-github/constraints/packaging-gte-26.2
Open

MAINT: Update packaging requirement from >=24.0 to >=26.2 in /.github/constraints#102
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/dot-github/constraints/packaging-gte-26.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github May 11, 2026

Copy link
Copy Markdown
Contributor

Updates the requirements on packaging to permit the latest version.

Release notes

Sourced from packaging's releases.

26.2

What's Changed

Fixes:

Documentation:

Internal:

New Contributors

Full Changelog: pypa/packaging@26.1...26.2

Changelog

Sourced from packaging's changelog.

26.2 - 2026-04-24


Fixes:
  • Fix incorrect sysconfig var name for pyemscripten in (:pull:1160)
  • Make Version, Specifier, SpecifierSet, Tag, Marker, and Requirement pickle-safe
    and backward-compatible with pickles created in 25.0-26.1 (including references to the removed
    packaging._structures module) (:pull:1163, :pull:1168, :pull:1170, :pull:1171)
  • Re-export ExceptionGroup in metadata for now in (:pull:1164)

Documentation:

  • Add errors section and fix missing details in (:pull:1159)
  • Document our property-based test suite in (:pull:1167)
  • Fix a DirectUrl typo in (:pull:1169)
  • Add example of is_unsatisfiable in (:pull:1166)

Internal:

  • Enable the auditor persona on zizmor in (:pull:1158)
  • Test new pickle guarantees in (:pull:1174)
  • Use new native ReadTheDocs uv integration in (:pull:1175)

26.1 - 2026-04-14

Features:

  • PEP 783: add handling for Emscripten wheel tags in (:pull:804) (old name used in implementation, fixed in next release)
  • PEP 803: add handling for the abi3.abi3t free-threading tag in (:pull:1099)
  • PEP 723: add packaging.dependency_groups module, based on the dependency-groups package in (:pull:1065)
  • Add the packaging.direct_url module in (:pull:944)
  • Add the packaging.errors module in (:pull:1071)
  • Add SpecifierSet.is_unsatisfiable using ranges (new internals that will be expanded in future versions) in (:pull:1119)
  • Add create_compatible_tags_selector to select compatible tags in (:pull:1110)
  • Add a key argument to SpecifierSet.filter() in (:pull:1068)
  • Support & and | for Marker's in (:pull:1146)
  • Normalize Version.__replace__ and add Version.from_parts in (:pull:1078)
  • Add an option to validate compressed tag set sort order in parse_wheel_filename in (:pull:1150)

Behavior adaptations:

  • Narrow exclusion of pre-releases for <V.postN to match spec in (:pull:1140)
  • Narrow exclusion of post-releases for >V to match spec in (:pull:1141)
  • Rename format_full_version to _format_full_version to make it visibly private in (:pull:1125)
  • Restrict local version to ASCII in (:pull:1102)

Pylock (PEP 751) updates:

... (truncated)

Commits

scipy>=1.13.0
scikit-learn>=1.5.0
packaging>=24.0
packaging>=26.2

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, we currently have this in src/gfdl/__init__.py:

packaging_version = Version(packaging.__version__)
min_packaging_version = "24.0"
if packaging_version < Version(min_packaging_version):
    raise ImportError(f"{packaging_version=}, but {min_packaging_version=}")

so we probably don't want to merge this without adjusting that. Does it make sense to require bleeding edge packaging? I'm not sure--maybe dependabot settings should be adjusted a bit more. Bleeding edge patches for the GitHub Actions CI addons seem fine (with the 1 week "cooldown" for supply chain security that we currently have set), but for the deps.txt file I'm less certain, and one question is who this file is really intended for. Typically one would want to have CI testing for lower and upper bounds of deps, but these >= requirements are always going to pull in the latest stable release of a given package.

That in itself has some security risk--we may want to also modify CI pip install commands to use --uploaded-prior-to and set the limit to at least 7 days old for supply chain security purposes (to avoid pulling in bleeding edge releases to CI that haven't been probed in the wild for a bit).

Of course we're a small project and maybe nobody cares, but I suspect doing the "right" thing is fairly low effort anyway.

Updates the requirements on [packaging](https://github.com/pypa/packaging) to permit the latest version.
- [Release notes](https://github.com/pypa/packaging/releases)
- [Changelog](https://github.com/pypa/packaging/blob/main/CHANGELOG.rst)
- [Commits](pypa/packaging@24.0...26.2)

---
updated-dependencies:
- dependency-name: packaging
  dependency-version: '26.2'
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/pip/dot-github/constraints/packaging-gte-26.2 branch from 7023b00 to 35cc49f Compare May 18, 2026 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant