| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Warning
The focused version pin addresses the documented CI failure without changing the existing execution condition.
0 open findings
What changed in this PRPins Python 3.13.15 in the multi-language PR check to avoid extractor failures with older CodeQL CLI versions.
Changes:
| File | Description |
|---|---|
| pr-checks/checks/multi-language-autodetect.yml | Updates the workflow template’s Python version and rationale. |
| .github/workflows/__multi-language-autodetect.yml | Generated counterpart; excluded from direct review. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
The "Multi-language repository" PR check is failing intermittently on ubuntu-latest for older CLI versions, for example in this run on main, with ImportError: cannot import name '_ERR_MSG' from 'importlib._bootstrap'.
The check installs Python 3.13 for these CLI versions because they don't work with Python 3.14 (#3212). Version 20261005.85 of the ubuntu-24.04 runner image has Python 3.13.16 in its toolcache, and 3.13.16 includes python/cpython@b0a181d8fc, a backport of the change that removed importlib._bootstrap._ERR_MSG in 3.14. Jobs that still run on the previous image get 3.13.15 and pass.
This PR pins the version to 3.13.15, which setup-python downloads on images that don't have it in their toolcache. The step's condition is unchanged, so newer CLI versions such as default also get 3.13.15, even though they don't need it.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Environments:
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist