Skip to content

upgrade mkdocs - #281

Merged
larskaare merged 1 commit into
mainfrom
upgrade-mkdocs
Oct 6, 2026
Merged

larskaare merged 1 commit into
mainfrom
upgrade-mkdocs

Conversation

@nimsilva

@nimsilva nimsilva commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@nimsilva
nimsilva requested review from aigelonic and a balanced review from Copilot and removed request for Copilot October 6, 2026 06:45

@larskaare larskaare left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Local testing summary

Checked out this branch and verified the dependency upgrade locally:

  • uv sync --locked --extra dev — installs cleanly from the updated lockfile with no resolution errors.
  • uv run mkdocs build --strict — builds successfully (exit 0).

Changes verified:

  • mkdocs-material: 9.7.6 → 9.7.7
  • mkdocs-techdocs-core: 1.7.0 → 1.7.1
  • pygments (transitive): 2.20.0 → 2.21.0

Only pyproject.toml and uv.lock are touched — no docs content changes.

For comparison, I also built main with the same command. Both builds produce the identical output:

  • An INFO note about a broken anchor link in toolbox/guidelines/secret-scanning.md (pre-existing, unrelated to this change)
  • The standard Material-for-MkDocs 2.0 deprecation notice

No new warnings or errors introduced by this upgrade. LGTM ✅

@larskaare
larskaare merged commit eb9aba1 into main Oct 6, 2026
3 checks passed
@larskaare
larskaare deleted the upgrade-mkdocs branch October 6, 2026 11:34
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