Skip to content

build: pin mkdocs<2 to stay clear of the MkDocs 2.0 rewrite#21

Merged
lesnik512 merged 1 commit into
mainfrom
pin-mkdocs
Jun 28, 2026
Merged

build: pin mkdocs<2 to stay clear of the MkDocs 2.0 rewrite#21
lesnik512 merged 1 commit into
mainfrom
pin-mkdocs

Conversation

@lesnik512

Copy link
Copy Markdown
Member

Why

The Material for MkDocs team is warning about MkDocs 2.0, a backward-incompatible ground-up rewrite of the core framework: it removes the plugin system, rewrites theming (breaking custom_dir overrides), switches config to TOML, and has no migration path — Material ceases to work entirely. It's also currently unlicensed. See their analysis.

This site relies on exactly what 2.0 breaks (overrides/main.html, extra_css, markdown extensions).

What

  • Add an explicit mkdocs>=1.6,<2 constraint.
  • Bump mkdocs-material floor to >=9.7.5 — the release that introduced the mkdocs<2 cap — so a fresh resolve can never pull MkDocs 2.0.
  • Relock (uv.lock): resolves to mkdocs 1.6.1 / mkdocs-material 9.7.6, unchanged from today.

Verification

  • uv lockmkdocs 1.6.1, mkdocs-material 9.7.6
  • uv run mkdocs build → clean

A Zensical (the Material team's successor) migration was spiked and shelved on spike/zensical — it's viable but still alpha, so we stay on MkDocs 1.x for now.

🤖 Generated with Claude Code

MkDocs 2.0 is a backward-incompatible rewrite (no plugin system, no theme
overrides, no migration path) that breaks Material for MkDocs. Material 9.7.5+
already caps mkdocs<2; make that explicit and bump the Material floor so a fresh
resolve can never pull MkDocs 2.0. Docs continue to build on mkdocs 1.6.1 /
mkdocs-material 9.7.6.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@lesnik512 lesnik512 merged commit bbd7e39 into main Jun 28, 2026
1 check passed
@lesnik512 lesnik512 deleted the pin-mkdocs branch June 28, 2026 21:04
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.

1 participant