Skip to content

chore(deps): bump pymdown-extensions to 11.0.1 via uv override - #51

Merged
TomKaltofen merged 1 commit into
mainfrom
chore/deps-pymdown-extensions
Jul 28, 2026
Merged

chore(deps): bump pymdown-extensions to 11.0.1 via uv override#51
TomKaltofen merged 1 commit into
mainfrom
chore/deps-pymdown-extensions

Conversation

@TKaltofen

Copy link
Copy Markdown
Collaborator

Clears the one open Dependabot alert on this repo.

What was blocking it

pymdown-extensions is transitive here (marimo). The b64 path-traversal advisory is fixed only in 11.0, and there is no patched 10.x. marimo declares pymdown-extensions>=10.21.2,<11, so uv lock --upgrade-package pymdown-extensions is a no-op: a constraint cannot beat an upper pin.

Note that the open grouped Dependabot PR #50 does not touch this package (it bumps mypy and grand-cypher), so it is not the fix despite being green.

What this does

Adds override-dependencies = ["pymdown-extensions>=11.0.1"] to [tool.uv] and relocks. Resolves 10.21.3 -> 11.0.1.

The 11.0 break is b64 restricting relative links to base_path by default (that is the fix) plus dropping Python 3.9, which is below this project's floor.

The lock diff also carries a few incidental marker refinements (cffi, exceptiongroup, pyzmq) from the relock. Remove the override once marimo allows 11.x.

Verification

tox: 1038 passed, 57 skipped; ruff format, ruff check, mypy --strict and bandit all clean.

marimo pins pymdown-extensions<11 and the fix for the b64 extension
path-traversal advisory ships only in 11.0, so a constraint cannot reach it.
Override the pin in [tool.uv] until marimo allows 11.x.
@TomKaltofen
TomKaltofen merged commit e337623 into main Jul 28, 2026
10 checks passed
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.

2 participants