Bump mkdocs-material from 8.2.3 to 8.2.4

[dependabot]

Bumps mkdocs-material from 8.2.3 to 8.2.4.

Release notes

Sourced from mkdocs-material's releases.

mkdocs-material-8.2.4

• Fixed malformed Google Fonts URL when a font setting was omitted
• Fixed #3648: Fixed specificity issue with admonitions in lists
• Fixed #3653: Invalid outdated version banner URL when using instant loading

Changelog

Sourced from mkdocs-material's changelog.

mkdocs-material-8.2.4+insiders-4.10.1 (2022-03-02)

• Added missing build dependencies to Dockerfile
• Fixed encoding issues in privacy plugin, now forcing UTF-8 encoding
• Fixed #3624: Scroll to active navigation item unreliable in Firefox
• Fixed #3642: Privacy plugin errors when font setting was omitted

mkdocs-material-8.2.4 (2022-03-02)

• Fixed malformed Google Fonts URL when a font setting was omitted
• Fixed #3648: Fixed specificity issue with admonitions in lists
• Fixed #3653: Invalid outdated version banner URL when using instant loading

mkdocs-material-8.2.3+insiders-4.10.0 (2022-02-27)

• Added support for offline plugin (supersedes offline search support)
• Improved built-in privacy plugin to download nested JavaScript assets
• Refactored configuration of built-in privacy plugin

mkdocs-material-8.2.3 (2022-02-27)

• Fixed #3578: Active element in table of contents off-by-one on large screens

mkdocs-material-8.2.2 (2022-02-26)

• Added automatic removal of query parameter when search is closed
• Fixed #3599: Anchors always overriden when using navigation tracking

mkdocs-material-8.2.1+insiders-4.9.1 (2022-02-21)

• Fixed #3610: missing lxml dependency for privacy plugin
• Fixed error when charset is missing in content-type header

mkdocs-material-8.2.1+insiders-4.9.0 (2022-02-20)

• Added privacy plugin: automatic downloading of external assets

mkdocs-material-8.2.1 (2022-02-17)

• Fixed module 'material.plugins' not being found (8.2.0 regression)

mkdocs-material-8.2.0 (2022-02-17)

• Added native support for Mermaid.js diagrams
• Added native support for tags (with search integration)
• Added support for staying on page when switching versions

mkdocs-material-8.1.11+insiders-4.8.3 (2022-02-13)

• Fixed #3560: Mermaid diagrams don't render for file:// locations

... (truncated)

Commits

• 2b32493 Prepare 8.2.4 release
• cb95798 Documentation
• a8c8c22 Added Elli to premium sponsors
• bcc2c18 Fixed invalid outdated version banner URL when using instant loading
• 1cc2506 Fixed specificity issue with admonitions in lists (#3648)
• 60f586f Documentation
• 64e5ed0 Fixed malformed Google Fonts url when a font setting was omitted
• 791c69a Documentation
• dfeb962 Updated dependencies
• f7a1111 Documentation
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.txt : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[codecov]

Codecov Report

Merging #41 (ba373e1) into main (1ec722b) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #41   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         4           
  Lines           85        85           
  Branches         8         8           
=========================================
  Hits            85        85           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1ec722b...ba373e1. Read the comment docs.

[dependabot]

Superseded by #43.