Skip to content

build: drop the django42 test dependency group - #39374

Merged
UsamaSadiq merged 2 commits into
openedx:masterfrom
feanil:feanil/drop-django42-group
Nov 14, 2026
Merged

UsamaSadiq merged 2 commits into
openedx:masterfrom
feanil:feanil/drop-django42-group

Conversation

@feanil

@feanil feanil commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Drops the django42 dependency group and empties the [tool.uv].conflicts set that paired it with django52, leaving a note on how to repopulate it when two Django versions are tested at once.

Nothing in CI selects the group: migrations-check.yml and unit-tests.yml only run django-version: "pinned", which resolves Django through the testing group's own Django<6.0 constraint. The group's only effect was on uv.lock, where the conflict set forced a second resolution for every package whose newest release has dropped Django 4.2. lti-consumer-xblock 11.5.0 (django>=5.2) was the latest one: #39373 locked 11.4.4 for django42 and 11.5.0 for everything else, and the bot's summary listed the package four times.

With the group gone, eight packages collapse to the single version the pinned environment already installs: django, django-autocomplete-light, django-filter, django-ipware, django-simple-history, edx-auth-backends, event-tracking, lti-consumer-xblock. No package in the pinned set changes version; uv lock --check is clean.

Preserved: the django52 group, for a future explicit-version matrix leg, and the bare Django runtime requirement with its <6.0 constraint. This changes what we test, not what the platform declares it runs on.

feanil and others added 2 commits November 13, 2026 15:47
Nothing in CI selects it: migrations-check.yml and unit-tests.yml only
run django-version "pinned", which resolves Django through the testing
group's own Django<6.0 constraint (5.2.x today). The group's only effect
was on uv.lock, where the django42/django52 conflict set forced a second
resolution for every package whose newest release no longer supports
Django 4.2. lti-consumer-xblock 11.5.0 (django>=5.2) was the latest:
the 2026-11-13 requirements bump (openedx#39373) locked 11.4.4 for django42 and
11.5.0 for everything else.

Removing the group and the [tool.uv].conflicts entry collapses those
packages to the version the pinned environment already installs
(django, django-autocomplete-light, django-filter, django-ipware,
django-simple-history, edx-auth-backends, event-tracking,
lti-consumer-xblock); no package in the pinned set changes version.
The django52 group stays for a future explicit-version matrix leg.

Co-Authored-By: Claude Fable 5.1 <[email protected]>
@feanil
feanil marked this pull request as ready for review November 13, 2026 20:52
@feanil
feanil requested a review from a team November 13, 2026 20:52
@UsamaSadiq
UsamaSadiq merged commit 16b6a79 into openedx:master Nov 14, 2026
42 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants