Repository navigation
Bump CI dependencies and fix Pygments steps after spec-prod - #372
Merged
Merged
Conversation
…eter w3c/spec-prod sets up its own Python and leaves it first on the PATH, so the "Generate *_messages.html" steps that run after the first spec-prod step picked up an interpreter without Pygments and failed with "ModuleNotFoundError: No module named 'pygments'". Call the interpreter installed by actions/setup-python through its python-path output instead of a bare `python`. Also bump actions/checkout and actions/setup-python to v7 and the in-repo Python to 3.15. w3c/spec-prod@v2 already resolves to the latest release (v2.14.1).
anssiko
approved these changes
Oct 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The later
Generate *_messages.htmlsteps fail with:w3c/spec-prodsets up its own Python (3.12) and leaves it first on thePATH. After the first spec-prod step, a barepythonno longer means the interpreteractions/setup-pythoninstalled Pygments into.Changes
python-pathoutput for thepip installand all threepygmentize_dir.pysteps.actions/checkoutv6 → v7. The only breaking change blocks fork checkouts underpull_request_targetandworkflow_run, which we don't use.actions/setup-pythonv6 → v7. The only breaking change removes thepip-installinput, which we don't use.w3c/spec-prod@v2is unchanged. It already resolves to the latest release, v2.14.1, and there is no v3.