Repository navigation
fix(explainer-video): declare the Python 3.14 ceiling with below #9685
Description
Part of #6017
Problem
explainer-video supports Python 3.12 and 3.13 only (plugins/explainer-video/scripts/pydeps.py, PYTHONS), but plugins/explainer-video/prerequisites.json declares only "min": "3.12" for the python entry, so a host whose only Python is 3.14 reports the row ready while the install hook cannot run there.
Scope
- Add
"below": "3.14"to thepythonentry'sdetect.versioninplugins/explainer-video/prerequisites.json. - Bump explainer-video (or add its changelog fragment) per repo convention.
Needs the below key from the prerequisites slice (blocked-by edge).
Done when
-
node -e 'const p=require("./plugins/explainer-video/prerequisites.json");const v=p.requires.find(r=>r.id==="python").detect.version;process.exit(v.min==="3.12"&&v.below==="3.14"?0:1)'exits 0. -
node scripts/check-declared-prerequisites.mjsexits 0. - A test (in
lib/prerequisites.test.mjsor the explainer-video check suite) runs the python entry against a stubbedPython 3.14.0version string and asserts statusoutdated, and againstPython 3.13.5and assertspresent;bash scripts/affected-tests.sh --runexits 0.
Activity
github-actions commentedon Oct 24, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; a maintainer confirms or changes it.
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Understood: explainer-video's prerequisites.json declares only a minimum Python of 3.12, so a host with only Python 3.14 reports ready although the install hook supports only 3.12 and 3.13. The fix is to add
"below": "3.14"to the python entry, add the version bump or changelog fragment, and add a test covering 3.14.0 (outdated) and 3.13.5 (present). The issue notes it depends on thebelowkey from the prerequisites slice. Nothing is missing. No duplicates found in the open issues.Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Oct 24, 2026
Not admitted to the issue lane yet: blocker #9684 is not closed as completed by a listed human or a merge.
melodic-automation-lanes commentedon Oct 25, 2026
The token broker refused the work-resolve-issue run that
agent-readystarted because the lanes kill switch was on, so it did no work. work-unblock removed and addedagent-readyback to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last addedagent-readyor a run last reported, work-unblock waits longer before each one, up to 24 hours.