requirements.txt

# The following are something akin to peer dependencies. They are represented
# as ranges in order to support interoperability with other mkdocs plugins or
# packages that might otherwise exist in an adopter's environment.
# mkdocs is capped below 2.0: MkDocs 2.0 is a ground-up rewrite with no plugin
# system and TOML-based config, and is incompatible with techdocs-core and
# Material for MkDocs. See:
# https://squidfunk.github.io/mkdocs-material/blog/2026/02/18/mkdocs-2.0/
mkdocs>=1.6,<2
Markdown>=3.2,<3.12

# The following are more akin to direct dependencies. Each line represents one
# or more features that are provided by `techdocs-core`, and thus are always
# pinned to an exact version. Bumps should be accompanied by release notes
# explaining what was added or fixed (or at least pointing to the underlying
# release notes of the bumped package).
mkdocs-material==9.7.7
markdown-graphviz-inline==1.1.3
mkdocs-github-admonitions-plugin==0.1.1
mkdocs-monorepo-plugin==1.1.2
plantuml-markdown==3.11.3
mdx_truly_sane_lists==1.3
pymdown-extensions==12.3
pygments==2.21.0
mkdocs-redirects==1.2.3

# The following are temporary dependencies that are only necessary to work
# around incompatible/conflicting underlying dependencies. Each dependency
# should include a comment explaining why it is needed, and under what
# circumstances it can be removed in the future.
# Exclude click 8.3.* which broke mkdocs serve autoreload (fixed in 8.4.0).
# Other bounds are inherited from transitive deps (e.g. mkdocs).
# https://github.com/squidfunk/mkdocs-material/issues/8478
# https://github.com/pallets/click/issues/3403
click!=8.3.*