Bump mkdocs-material from 7.3.5 to 7.3.6

[dependabot]

Bumps mkdocs-material from 7.3.5 to 7.3.6.

Release notes

Sourced from mkdocs-material's releases.

mkdocs-material-7.3.6

• Added support for adding titles to code blocks

Changelog

Sourced from mkdocs-material's changelog.

mkdocs-material-7.3.6+insiders-3.2.0 (2021-10-31)

• Added support for feedback widget (Was this page helpful?)

mkdocs-material-7.3.6 (2021-10-30)

• Added support for adding titles to code blocks

mkdocs-material-7.3.5+insiders-3.1.5 (2021-10-28)

• Fixed #3144: Rogue link when using tags with auto-populated navigation
• Fixed #3147: Code block line numbers appear in search results
• Fixed #3158: Social cards do not strip HTML tags from title

mkdocs-material-7.3.5 (2021-10-27)

• Added support for setting table of contents title via mkdocs.yml
• Fixed back-to-top button position for right-to-left languages

mkdocs-material-7.3.4+insiders-3.1.4 (2021-10-17)

• Fixed #2974: Text cropped with other fonts than Roboto in social plugin
• Fixed #3099: Encoding problems with non-latin character in social plugin
• Fixed #3112: Japanese segmenter not executed as part of new tokenizer
• Fixed tags (front matter) appearing in search with disabled tags plugin

mkdocs-material-7.3.4 (2021-10-17)

• Bumped MkDocs version to 1.2.3 to mitigate CVE-2021-40978
• Fixed spacing issues when using integrate table of contents with tabs
• Fixed some spacings issues for right-to-left languages
• Fixed race condition in search initialization

mkdocs-material-7.3.3+insiders-3.1.3 (2021-10-12)

• Added warnings to search plugin for unsupported options and syntax
• Fixed #3503: Search sometimes returns entire page
• Fixed #3089: Single-line code annotations disappear when printing

mkdocs-material-7.3.3 (2021-10-11)

• Rewrite of entire documentation
• Adjusted height of new content tabs to match single line code blocks
• Fixed new content tabs missing right padding in some browsers on overflow
• Fixed new content tabs bleeding out of flex container on overflow
• Fixed new content tabs overflow scrolling bugs on some browsers
• Fixed new content tabs stealing keyboard access when active
• Fixed some spacings issues for right-to-left languages

mkdocs-material-7.3.2+insiders-3.1.2 (2021-10-06)

... (truncated)

Commits

• 9b4de5d Prepare 7.3.6 release
• 2ebda92 Documentation
• a57869d Documentation
• c422bd7 Documentation
• a532755 Added note on --dirtyreload flag
• 6ceef24 Added support for code block titles
• cb3220b Updated dependencies
• 37fe21e Excluded template changes from search results
• 6485305 Updated Insiders changelog
• See full diff 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.