Bump the python-locks-all group across 1 directory with 2 updates

[dependabot]

Bumps the python-locks-all group with 2 updates in the / directory: mkdocs-git-revision-date-localized-plugin and pymdown-extensions.

Updates mkdocs-git-revision-date-localized-plugin from 1.5.4 to 1.6.0

Release notes

Sourced from mkdocs-git-revision-date-localized-plugin's releases.

v1.6.0

Highlights

Faster builds

Every page asked git which tag pointed at its commit, and asked again for the site-wide revision commit — the same answer, recomputed for each page. Those lookups are now cached.

The bigger your site, the more you save: on a 1000 page site this removes roughly 18 seconds of build time.

custom_format keeps your own words

If your format had any text around the date directives, that text came out scrambled:

custom_format: "Updated on %d %B %Y"

before:   Up23AMt723 on 23 January 2022
now:      Updated on 23 January 2022

Any format that was made up purely of % directives (including the %d. %B %Y default) was unaffected and still renders exactly as before. Unrecognised directives such as %Q are now left alone instead of being quietly reinterpreted as a different date field.

Creation date commit hash and tag now work

page.meta.git_creation_date_localized_hash and page.meta.git_creation_date_localized_tag were documented but always came back empty. If you use them in a theme override to link back to the commit or release that introduced a page, they now contain what you expect.

Shallow clone warnings reach more setups

The warning that tells you your dates will be wrong because CI only fetched part of the history was silently skipped whenever your .git was not in the directory you ran mkdocs from — a repository inside docs/, or a temporary checkout made by plugins such as monorepo. It now fires there too.

Clearer messages when something goes wrong

• A bad type: now produces a proper MkDocs config error listing the valid values, instead of a bare AssertionError.
• If reading git history in parallel fails, the error explains what enable_parallel_processing: false actually does, rather than suggesting a fallback it never attempted.
• Plugin messages now go through MkDocs' own logger, so they are formatted and coloured like every other message in your build output.

Type hints are now visible

The package ships py.typed, so mypy, pyright and ty can see the plugin's annotations.

Upgrading

mkdocs build --strict is now stricter. Warnings from this plugin previously bypassed MkDocs' warning counter, so --strict ignored them. They now count.

In practice this means a build that combines --strict with a shallow clone will start failing where it used to pass — most commonly GitHub Actions, which checks out with fetch-depth: 1 by default. The dates in that build really are wrong, so the right fix is to fetch the full history:

- uses: actions/checkout@v6
</tr></table> 

... (truncated)

Commits

• 8db2449 Bump version to 1.6.0
• 1f6eb6d Merge pull request #226 from timvink/refactor/page-rendering-and-packaging
• 604005a Merge pull request #224 from timvink/fix/date-formatting-and-git-detection
• 6e9e4e4 Cache tag lookups, split up on_page_markdown, tidy packaging
• bf270f7 Fix custom_format literals, creation commit hash and shallow clone detection
• 97ecbac Bump mkdocs-material from 9.7.6 to 9.7.7 (#223)
• See full diff in compare view

Updates pymdown-extensions from 11.0.2 to 12.1

Release notes

Sourced from pymdown-extensions's releases.

12.1

• NEW: SuperFences: Add optional reset function that can be specified for custom fences.
• FIX: Tilde, Caret: Fix performance for long invalid delimiters.

12.0.1

• FIX: BetterEm: fix a case with new logic.

12.0

• BREAK: BetterEm: Complete rewrite. There may be some subtle differences between legacy behavior and new CommonMark behavior.

  • * and _ emphasis are handled at the same time to provide more natural nesting.
  • More performant.
  • CommonMark compliant.

• BREAK: Tilde, Caret, Mark: Rewritten and now built upon the latest BetterEm logic.

  • When used with BetterEm, Tilde, Caret, and Mark will be added to the same delimiter processor under the hood and will be parsed at the same time as emphasis, allowing for better nesting logic.
  • More performant. Performance issues reported by (@​lexdotdev).
  • Tilde, Caret, Mark: Allow deletion, insertions, and marking mid-word by default. Set smart_delete, smart_insert, or smart_mark, respectively, to enable previous behavior, which prevented mid-word deletion.
  • Tilde, Caret: Add new option no_space to control whether the Pandoc style requirement of "no unescaped spaces" is enabled for subscript and superscript, respectively. no_space is enabled by default.

• NEW: Details, Blocks.Details, Blocks.Admonitions: Allow and handle headers specially in titles.

• NEW: Quotes: Allow and handle headers specially in callout titles.

• NEW: BracketSpan: New extension that allows for the creation of spans using a Pandoc style bracket notation.

• NEW: Arithmatex: Remove deprecated inline_mathjax_preview_format, inline_mathjax_format, and inline_generic_format. Use arithmatex_inline_format instead.

• NEW: Arithmatex: Remove deprecated fence_mathjax_preview_format, fence_mathjax_format, and fence_generic_format. Use arithmatex_fenced_format instead.

• NEW: Emoji: Remove undocumented and deprecated "old style" custom emoji index logic.

• NEW: Slugs: Remove deprecated uslugify, uslugify_encoded, uslugify_cased, uslugify_cased_encoded, gfm, and gfm_encoded. Use the documented slugify method with appropriate arguments instead.

Commits

• 9b896a8 Docs: Update theme
• 3cb89bb Fix Tilde, Caret performance with long, invalid delimiters
• d3d1f90 Docs: Update theme
• 5c4a3af Update version
• 2341405 Add configurable reset function for custom fences
• 0e0060d Update changelog
• 136d324 Add test for a fixed case in previous commit
• 8087e9b Reduce duplicate code and simplify space accounting in Tilde and Caret
• b613e7f More grammar fixes
• ddcbb1d Fix grammar
• Additional commits viewable in compare view

---

Note

Medium Risk
pymdown-extensions 12.x can subtly change Markdown rendering for enabled extensions; the git-revision plugin may surface warnings that --strict treats as failures if git history or config is incomplete.

Overview
Bumps the documentation lockfile by raising minimum versions in requirements-docs.in and recompiling requirements-docs.txt: mkdocs-git-revision-date-localized-plugin 1.5.4 → 1.6.0 and pymdown-extensions 11.0.2 → 12.1.

The git-revision plugin upgrade mainly affects MkDocs build behavior (cached tag lookups, stricter handling of plugin warnings under mkdocs build --strict, and fixes around date formatting and creation-date metadata). This repo’s docs CI already checks out with fetch-depth: 0 before mkdocs build --strict, so the shallow-clone strict failure mode is less likely here than on default shallow checkouts.

pymdown-extensions 12.x is a larger jump: BetterEm and related Tilde/Caret/Mark parsing were rewritten for CommonMark-style nesting and can change how emphasis, strikethrough, insertions, and highlights render in pages that use those extensions (as configured in mkdocs.yml).

^{Reviewed by Cursor Bugbot for commit 7c7904a. Bugbot is set up for automated code reviews on this repo. Configure here.}