Skip to content

build: hold requirements at Python 3.11 until the LMS moves to 3.12 - #241

Open
jristau1984 wants to merge 3 commits into
masterfrom
jristau/requirements-bot-python-3.11
Open

jristau1984 wants to merge 3 commits into
masterfrom
jristau/requirements-bot-python-3.11

Conversation

@jristau1984

@jristau1984 jristau1984 commented Nov 21, 2026 •

Copy link
Copy Markdown
Contributor

What

Hold the requirements bot at Python 3.11 for compiling pins, while testing on 3.11 and 3.12.

Why

We're moving to Python 3.12, but edx.org's LMS still runs 3.11 (the edx-platform image is on Ubuntu focal with vendored Python 3.11; see BOMS-239). Code installed into the LMS has to stay installable on 3.11 until that changes.

The shared upgrade-python-requirements workflow compiles on 3.12, which pins versions that require Python >=3.12 (for example edx-django-utils==8.2.0, code-annotations==3.0.0, sphinx==9.1.1). Those can't install on 3.11, so the bot's PRs fail (see #240).

Rule of thumb: compile pins on the oldest supported Python, test on all supported versions.

This PR also adds 3.12 to the quality workflow's matrix (fail-fast: false), so CI shows whether devstack's tooling is ready for 3.12 without blocking on it.

When the LMS moves to 3.12

Switch python_version to "3.12" here and drop 3.11 from the test matrix.

After merge

Close #240 and run the "Upgrade Requirements" workflow manually for a fresh PR compiled on 3.11.

Generated with Claude Code on behalf of @jristau1984.

🤖 Generated with Claude Code

The shared upgrade-python-requirements workflow defaults to Python 3.12, so
the requirements bot pins versions that need 3.12 (e.g. edx-django-utils 8.2,
code-annotations 3.0, sphinx 9.1). CI and edx.org's LMS run Python 3.11, so
those pins fail to install and every bot PR goes red.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jristau1984 jristau1984 changed the title build: compile requirements with Python 3.11 to match production build: hold requirements at Python 3.11 until the LMS moves to 3.12 Nov 21, 2026
jristau1984 and others added 2 commits November 20, 2026 23:35
Keeps requirements compiled on 3.11 (what edx.org runs today) while showing
whether devstack's tooling is ready for 3.12.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nputs

The previous commit put python_version under workflow_dispatch.inputs.branch,
which made the YAML invalid. Move it into the reusable workflow job's with block.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jristau1984
jristau1984 force-pushed the jristau/requirements-bot-python-3.11 branch from eed14e7 to f7a8def Compare November 21, 2026 04:35
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.

1 participant