Skip to content

build: bump importlib-metadata from 4.6.4 to 9.0.0 in /requirements - #754

Open
blaipr wants to merge 1 commit into
ctrliq:mainfrom
blaipr:build/bump-importlib-metadata-9.0.0-requirements
Open

build: bump importlib-metadata from 4.6.4 to 9.0.0 in /requirements#754
blaipr wants to merge 1 commit into
ctrliq:mainfrom
blaipr:build/bump-importlib-metadata-9.0.0-requirements

Conversation

@blaipr

@blaipr blaipr commented Aug 26, 2026

Copy link
Copy Markdown
Contributor
SUMMARY

Bumps importlib-metadata from 4.6.4 to 9.0.0 in requirements/requirements.txt. It reads installed distribution metadata; the collection and plugin loaders use it.

The Python requirements are outside Dependabot's scope on purpose: #675 turned on version updates for github-actions and for npm in /awx/ui and left this file out, because it is compiled by requirements/updater.sh rather than hand-pinned. So this was produced the same way make requirements produces it:

# requirements.in:  importlib-metadata==4.6.4  ->  importlib-metadata==9.0.0
requirements/updater.sh run

run inside the ascender_devel image, which is where that script insists on running. Pinned with == in requirements.in, so upgrade cannot move it: the pin is edited first and run recompiles against it. The result is 1 added / 1 removed in each of the two files.

This is the largest jump in the set and the pin is the oldest: 4.6.4 is from 2021, and like packaging==24.2 it carries no comment saying why. The unit suite passes on 9.0.0, but that only covers the import paths those tests reach, so this one deserves a closer look than the patch bumps beside it. Happy to close it if the pin turns out to be load-bearing for something the tests do not touch.

ISSUE TYPE
  • Bug, Docs Fix or other nominal change
COMPONENT NAME
  • API
ASCENDER VERSION
25.5.1

Tests

Tested before opening, in the same image, with importlib-metadata 9.0.0 installed into the AWX venv:

py.test awx/main/tests/unit awx/conf/tests/unit awx/sso/tests/unit
  1404 passed, 1 skipped in 10.94s

CI does not run on pull requests from a fork until a maintainer approves the workflow, so this is what stands behind the change until then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant