Bump mkdocs-material from 8.1.4 to 8.1.7

[dependabot]

Bumps mkdocs-material from 8.1.4 to 8.1.7.

Release notes

Sourced from mkdocs-material's releases.

mkdocs-material-8.1.7

• Improved back-to-top button behavior - now not shown on anchor jump

mkdocs-material-8.1.6

• Fixed spacing of blockquotes (8.1.5 regression)
• Fixed edge cases for rounded corners on code blocks (8.1.5 regression)
• Fixed issues with code annotation line heights

mkdocs-material-8.1.5

• Improved browser support: Chrome 49+, Safari 10+, Firefox 53+, Edge 79+
• Improved rendering of inline code blocks in headlines
• Added Bahasa Malaysian translations
• Fixed #3354: MathJax formulas show vertical scrollbar

Changelog

Sourced from mkdocs-material's changelog.

mkdocs-material-8.1.7+insiders-4.6.1 (2022-01-16)

• Fixed #3459: Section index pages picking up wrong title

mkdocs-material-8.1.7 (2022-01-16)

• Improved back-to-top button behavior - now not shown on anchor jump

mkdocs-material-8.1.6-insiders-4.6.0 (2022-01-11)

• Added support for annotations (outside of code blocks)

mkdocs-material-8.1.6 (2022-01-11)

• Fixed spacing of blockquotes (8.1.5 regression)
• Fixed edge cases for rounded corners on code blocks (8.1.5 regression)
• Fixed rendering issues with code annotation line heights

mkdocs-material-8.1.5 (2022-01-09)

• Improved browser support: Chrome 49+, Safari 10+, Firefox 53+, Edge 79+
• Improved rendering of inline code blocks in headlines
• Added Bahasa Malaysian translations
• Fixed #3354: MathJax formulas show vertical scrollbar

mkdocs-material-8.1.4+insiders-4.5.2 (2022-01-08)

• Fixed #3440: Content tab indicator not moving when using linking
• Fixed #3445: Content tab switch flickers/jitters when using linking

mkdocs-material-8.1.4+insiders-4.5.1 (2022-01-02)

• Added support for setting initial state of cookie consent
• Fixed #3396: Disappearing link in navigation due to Safari bug

mkdocs-material-8.1.4 (2022-01-02)

• Added indicator to navigation expander icon
• Improved support for reduced motion preference
• Fixed jitter of active content tab indicator

mkdocs-material-8.1.3 (2021-12-19)

• Added animation to active content tab indicator
• Fixed #3360: Highlighted lines add blank lines in copied text
• Fixed usage of subsequent index files when using section index pages

mkdocs-material-8.1.2+insiders-4.5.0 (2021-12-16)

• Added support for navigation icons

... (truncated)

Commits

• a919199 Updated Insiders changelog
• c74a886 Prepare 8.1.7 release
• 014ab60 Improved back-to-top button behavior on anchor jump
• 0a08e67 Added missing extends pragmas
• 2231aab Added extension pragma
• 749c19c Fixed endless redirect in palette change example
• f9e9418 Added guide for setting up Giscus
• 29cc1dd Documentation
• 9511569 Added dark mode support for Giscus
• 09c0e1c Removed feedback section in blog for Giscus integration
• 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 #28 (5c8f932) into main (7a12b9b) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #28   +/-   ##
=========================================
  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 7a12b9b...5c8f932. Read the comment docs.

[dependabot]

Superseded by #30.