dependabot[bot] opened a new pull request, #1798: URL: https://github.com/apache/streampipes/pull/1798
Bumps [mkdocs](https://github.com/mkdocs/mkdocs) from 1.4.2 to 1.5.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/mkdocs/mkdocs/releases";>mkdocs's releases</a>.</em></p> <blockquote> <h2>1.5.0</h2> <p><strong>New: MkDocs now accepts donations.</strong> Please consider supporting the current maintainer at my new GitHub sponsorship page.</p> <p>MkDocs has been a totally free project since the beginning and wasn't accepting funds. MkDocs will remain free of paywalls, but now you can show your support with donations (one-time and/or recurring).</p> <p><a href="https://github.com/sponsors/oprypin";><strong><code>Donate for MkDocs - @oprypin sponsors page</code></strong></a></p> <p>And please also consider these other individuals who have been contributing to the ecosystem for a long time and check out their donations pages:</p> <p><a href="https://github.com/sponsors/facelessuser";><code>@facelessuser</code></a> <a href="https://github.com/sponsors/pawamoy";><code>@pawamoy</code></a> <a href="https://github.com/sponsors/Ultrabug";><code>@Ultrabug</code></a></p> <hr /> <h3>Release 1.5.0</h3> <h2>New command <code>mkdocs get-deps</code></h2> <p>This command guesses the Python dependencies that a MkDocs site requires in order to build. It simply prints the PyPI packages that need to be installed. In the terminal it can be combined directly with an installation command as follows:</p> <pre lang="bash"><code>pip install $(mkdocs get-deps) </code></pre> <p>The idea is that right after running this command, you can directly follow it up with <code>mkdocs build</code> and it will almost always "just work", without needing to think which dependencies to install.</p> <p>The way it works is by scanning <code>mkdocs.yml</code> for <code>themes:</code>, <code>plugins:</code>, <code>markdown_extensions:</code> items and doing a reverse lookup based on a large list of known projects (catalog, see below).</p> <p>Of course, you're welcome to use a "virtualenv" with such a command. Also note that for environments that require stability (for example CI) directly installing deps in this way is not a very reliable approach as it precludes dependency pinning.</p> <p>The command allows overriding which config file is used (instead of <code>mkdocs.yml</code> in the current directory) as well as which catalog of projects is used (instead of downloading it from the default location). See <a href="https://www.mkdocs.org/user-guide/cli/#mkdocs-get-deps";><code>mkdocs get-deps --help</code></a>.</p> <p>Context: <a href="https://redirect.github.com/mkdocs/mkdocs/issues/3205";>#3205</a></p> <h2>MkDocs has an official catalog of plugins</h2> <p>Check out <a href="https://github.com/mkdocs/catalog";>https://github.com/mkdocs/catalog</a> and add all your general-purpose plugins, themes and extensions there, so that they can be looked up through <code>mkdocs get-deps</code>.</p> <p>This was renamed from "best-of-mkdocs" and received significant updates. In addition to <code>pip</code> installation commands, the page now shows the config boilerplate needed to add a plugin.</p> <h2>Expanded validation of links</h2> <h3>Validated links in Markdown</h3> <blockquote> <p>As you may know, within Markdown, MkDocs really only recognizes <strong>relative</strong> links that lead to another physical <code>*.md</code> document (or media file). This is a good convention to follow because then the source pages are also freely browsable without MkDocs, for example on GitHub. MkDocs knows that in the output it should turn those <code>*.md</code> links into <code>*.html</code> as appropriate, and it would also always tell you if such a link doesn't actually lead to an existing file.</p> </blockquote> <p>However, the checks for links were really loose and had many concessions. For example, links that started with <code>/</code> ("absolute") and links that <em>ended</em> with <code>/</code> were left as is and no warning was shown, which allowed such very fragile links to sneak into site sources: links that happen to work right now but get no validation and links that confusingly need an extra level of <code>..</code> with <code>use_directory_urls</code> enabled.</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/mkdocs/mkdocs/commit/0d9e3414e128b1fb1397c22ef60846f762b45a01";><code>0d9e341</code></a> Release 1.5.0 (<a href="https://redirect.github.com/mkdocs/mkdocs/issues/3296";>#3296</a>)</li> <li><a href="https://github.com/mkdocs/mkdocs/commit/0f8ab6bd6fbbf6d22517e1e63e79f0c62e7803a5";><code>0f8ab6b</code></a> Fix livereload shutdown sequence - crash on Windows</li> <li><a href="https://github.com/mkdocs/mkdocs/commit/bfb52a30acfd98f8cabb3f78985755b6c19eb1be";><code>bfb52a3</code></a> Create FUNDING.yml (<a href="https://redirect.github.com/mkdocs/mkdocs/issues/3295";>#3295</a>)</li> <li><a href="https://github.com/mkdocs/mkdocs/commit/189faf03c1b0a83fe69d3e486d2b658c2629e875";><code>189faf0</code></a> Merge pull request <a href="https://redirect.github.com/mkdocs/mkdocs/issues/3297";>#3297</a> from mkdocs/regr</li> <li><a href="https://github.com/mkdocs/mkdocs/commit/bb00d4cebb6187c1eaab78384b886b32ce778d71";><code>bb00d4c</code></a> Add a test for relative link without dot in filename</li> <li><a href="https://github.com/mkdocs/mkdocs/commit/c3d4ff7b69801d40e4f75bf06c95aa641125566e";><code>c3d4ff7</code></a> Fix unescaping of Markdown titles</li> <li><a href="https://github.com/mkdocs/mkdocs/commit/d8bc90f11335413658586bf26f25a14a0de60d4d";><code>d8bc90f</code></a> Always set <code>inclusion_level</code> so static-i18n plugin keeps working</li> <li><a href="https://github.com/mkdocs/mkdocs/commit/80254454d268800658a4f113c9469c0ad1d99f94";><code>8025445</code></a> Revert "Check types against older Click that still has correct types"</li> <li><a href="https://github.com/mkdocs/mkdocs/commit/b1624b5ce816b1ae8a28e981f6ccaf9c8b15f6b4";><code>b1624b5</code></a> Add blockquote styling for mkdocs theme (<a href="https://redirect.github.com/mkdocs/mkdocs/issues/3291";>#3291</a>)</li> <li><a href="https://github.com/mkdocs/mkdocs/commit/41de1dd04be19cde793d5a4996cfa7373751e33c";><code>41de1dd</code></a> The new <code>!relative</code> tag also needs to be ignored in <code>get-deps</code></li> <li>Additional commits viewable in <a href="https://github.com/mkdocs/mkdocs/compare/1.4.2...1.5.0";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
