Bump mkdocs-build-plantuml-plugin from 1.9.0 to 2.1.0

[dependabot]

Bumps mkdocs-build-plantuml-plugin from 1.9.0 to 2.1.0.

Release notes

Sourced from mkdocs-build-plantuml-plugin's releases.

2.1.0

See CHANGELOG.md for details.

2.0.0

Breaking Changes

This release updates the example project to MkDocs Material 9.x, which requires changes to dark mode configuration.

If you copied the example setup, you need to update:

1. mkdocs.yml theme configuration - Material 9.x uses a different palette syntax:

   theme:
     name: material
     palette:
       - scheme: default
         toggle:
           icon: material/brightness-7
           name: Switch to dark mode
       - scheme: slate
         toggle:
           icon: material/brightness-4
           name: Switch to light mode

2. CSS dark mode selector - Change from @media(prefers-color-scheme: dark) to [data-md-color-scheme="slate"]

3. JavaScript theme detection - Update from matchMedia('prefers-color-scheme') to MutationObserver watching data-md-color-scheme attribute

4. PlantUML theme files - Add skinparam backgroundColor transparent for proper dark mode display

Added

• Test suite with pytest (unit and integration tests)
• GitHub Actions workflow for automated testing
• Transparent background support in PlantUML themes

Changed

• Updated example dependencies to current versions (Material 9.x, pymdown-extensions 10.12, etc.)
• Updated documentation for Material 9.x dark mode setup

Changelog

Sourced from mkdocs-build-plantuml-plugin's changelog.

[2.1.0] - 2026-02-24

Fixed

• Replace Path.walk() with os.walk() to restore Python < 3.12 compatibility (#45)
• Strip quotes from diagram names (e.g. @startuml "mydiagram") to prevent infinite regeneration during mkdocs serve (#41)
• Exclude .git and other configurable directories when walking diagram roots to prevent errors when diagram_root is set to . (#42)

Added

• New exclude_dirs config option (default: [".git"]) to skip directories during diagram discovery (#42)

Changed

• Bump python_requires from >=3.12 to >=3.10 (Python 3.8/3.9 are EOL; ecosystem deps require 3.10+)
• Move "Processing diagram" and "root dir / src dir" log messages from INFO to DEBUG level to reduce log noise in large projects (#38). Use mkdocs serve --verbose to see them.
• Extend CI matrix to cover Python 3.10–3.13

[2.0.0] - 2025-01-23

Breaking Changes

This release updates the example project to MkDocs Material 9.x, which requires changes to dark mode configuration.

If you copied the example setup, you need to update:

1. mkdocs.yml theme configuration - Material 9.x uses a different palette syntax:

   theme:
     name: material
     palette:
       - scheme: default
         toggle:
           icon: material/brightness-7
           name: Switch to dark mode
       - scheme: slate
         toggle:
           icon: material/brightness-4
           name: Switch to light mode

2. CSS dark mode selector - Change from @media(prefers-color-scheme: dark) to [data-md-color-scheme="slate"]

3. JavaScript theme detection - Update from matchMedia('prefers-color-scheme') to MutationObserver watching data-md-color-scheme attribute

4. PlantUML theme files - Add skinparam backgroundColor transparent for proper dark mode display

Added

• Test suite with pytest (unit and integration tests)

... (truncated)

Commits

• 02c4c27 chore: prepare release 2.1.0
• 4e8fb04 fix: reduce log noise by moving verbose output to debug level
• 1c3a306 fix: strip quotes from diagram names to prevent infinite regeneration
• 616eda8 feat: add exclude_dirs config option to skip directories during walk
• 4993ee6 fix: replace Path.walk() with os.walk() to support Python >= 3.8
• 0d6e3f5 ci: remove obsolete publishing workflows
• 1057810 ci: add PyPI trusted publishing workflow
• a982c5c docs: update README for PATH lookup, update example dependencies
• ba979b6 fix: fallback to 'plantuml' when not found in PATH
• 7afff7e Update README with bin_path clarification
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)