docs: pin Pygments==2.18.0 and bump pymdown-extensions to 10.14#19
Merged
Conversation
CI was failing on 'AttributeError: NoneType object has no attribute replace' inside pymdownx.highlight -> pygments.formatters.html.HtmlFormatter. Root cause: pymdown-extensions <= 10.11 passes filename=None to HtmlFormatter, which Pygments 2.19+ no longer tolerates. Local Windows builds happened to have Pygments 2.18.0 cached so the regression only surfaced on the GitHub Actions runner. Two-part fix: bump pymdown-extensions to 10.14 (which carries the upstream fix for the None-default), and explicitly pin Pygments==2.18.0 as belt-and-braces so a future Pygments minor that re-tightens the same surface cannot break the build silently. mkdocs-material 9.5.39 stays put; --strict build verified clean against all three pins.
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
1 participant
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.
CI was failing on 'AttributeError: NoneType object has no attribute replace' inside pymdownx.highlight -> pygments.formatters.html.HtmlFormatter. Root cause: pymdown-extensions <= 10.11 passes filename=None to HtmlFormatter, which Pygments 2.19+ no longer tolerates. Local Windows builds happened to have Pygments 2.18.0 cached so the regression only surfaced on the GitHub Actions runner.
Two-part fix: bump pymdown-extensions to 10.14 (which carries the upstream fix for the None-default), and explicitly pin Pygments==2.18.0 as belt-and-braces so a future Pygments minor that re-tightens the same surface cannot break the build silently. mkdocs-material 9.5.39 stays put; --strict build verified clean against all three pins.