dependabot[bot] opened a new pull request, #17824:
URL: https://github.com/apache/tvm/pull/17824

   Bumps [cleo](https://github.com/python-poetry/cleo) from 0.8.1 to 2.0.0.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/python-poetry/cleo/releases";>cleo's 
releases</a>.</em></p>
   <blockquote>
   <h2>2.0.0</h2>
   <p>No source code changes.</p>
   <p>This is a version-only release to replace <code>1.0.0</code>, which was 
yanked on the grounds that it was incompatible with real dependents (i.e. 
Poetry) based on their version specifiers, which explicitly included 
<code>1.0.0</code> pre-releases.</p>
   <h2>1.0.0</h2>
   <h3>Key points</h3>
   <ul>
   <li>Supported Python versions are now 3.7 up to 3.11.</li>
   <li><code>cleo</code> is now fully type-checked.</li>
   <li><code>cleo</code> no longer depends on <code>clikit</code>.</li>
   </ul>
   <h3>Changed</h3>
   <ul>
   <li>Replaced <code>Terminal</code> class with 
<code>shutil.get_terminal_size()</code> from standard library
   (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/175";>#175</a>).</li>
   <li>Exceptions are now Errors (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/179";>#179</a>).</li>
   <li><code>pylev</code> was dropped in favor of much faster 
<code>rapidfuzz</code> (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/173";>#173</a>).</li>
   <li>Default error verbosity was reduced (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/132";>#132</a> &amp; 
<a 
href="https://redirect.github.com/python-poetry/cleo/pull/166";>#166</a>).</li>
   </ul>
   <h3>Removed</h3>
   <ul>
   <li>Removed doc comment-based command configuration notation
   (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/239";>#239</a>).</li>
   </ul>
   <h3>Fixed</h3>
   <ul>
   <li><code>--no-interaction</code> is now automatically set when running in 
non-TTY terminals (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/245";>#245</a>).</li>
   <li>Generated completions will no longer cause shell errors for namespaced 
commands (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/247";>#247</a>).</li>
   <li>Using <code>^C</code> while autocompleting <code>Question</code> answer 
will no longer break terminal (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/240";>#240</a>).</li>
   <li>Namespaced commands no longer reset interactive state (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/234";>#234</a>).</li>
   <li>Fixed underlying regex that caused CVE-2022-42966 (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/285";>#285</a>).</li>
   </ul>
   <h2>1.0.0a5</h2>
   <p>No release notes provided.</p>
   <h2>1.0.0a4</h2>
   <p>No release notes provided.</p>
   <h2>1.0.0a3</h2>
   <p>No release notes provided.</p>
   <h2>1.0.0a2</h2>
   <p>No release notes provided.</p>
   <h2>1.0.0a1</h2>
   <p>No release notes provided.</p>
   </blockquote>
   </details>
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/python-poetry/cleo/blob/main/CHANGELOG.md";>cleo's 
changelog</a>.</em></p>
   <blockquote>
   <h2>[2.0.0] - 2022-11-21</h2>
   <p>No source code changes.</p>
   <p>This is a version-only release to replace <code>1.0.0</code>, which was 
yanked on the
   grounds that it was incompatible with real dependents (i.e. Poetry) based on
   their version specifiers, which explicitly included <code>1.0.0</code> 
pre-releases.</p>
   <h2>[1.0.0] - 2022-11-21</h2>
   <h3>Key points</h3>
   <ul>
   <li>Supported Python versions are now 3.7 up to 3.11.</li>
   <li><code>cleo</code> is now fully type-checked.</li>
   <li><code>cleo</code> no longer depends on <code>clikit</code>.</li>
   </ul>
   <h3>Changed</h3>
   <ul>
   <li>Replaced <code>Terminal</code> class with 
<code>shutil.get_terminal_size()</code> from standard library
   (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/175";>#175</a>).</li>
   <li>Exceptions are now Errors (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/179";>#179</a>).</li>
   <li><code>pylev</code> was dropped in favor of much faster 
<code>rapidfuzz</code> (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/173";>#173</a>).</li>
   <li>Default error verbosity was reduced (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/132";>#132</a> &amp; 
<a 
href="https://redirect.github.com/python-poetry/cleo/pull/166";>#166</a>).</li>
   </ul>
   <h3>Removed</h3>
   <ul>
   <li>Removed doc comment-based command configuration notation
   (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/239";>#239</a>).</li>
   </ul>
   <h3>Fixed</h3>
   <ul>
   <li><code>--no-interaction</code> is now automatically set when running in 
non-TTY terminals (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/245";>#245</a>).</li>
   <li>Generated completions will no longer cause shell errors for namespaced 
commands (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/247";>#247</a>).</li>
   <li>Using <code>^C</code> while autocompleting <code>Question</code> answer 
will no longer break terminal (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/240";>#240</a>).</li>
   <li>Namespaced commands no longer reset interactive state (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/234";>#234</a>).</li>
   <li>Fixed underlying regex that caused CVE-2022-42966 (<a 
href="https://redirect.github.com/python-poetry/cleo/pull/285";>#285</a>).</li>
   </ul>
   </blockquote>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/python-poetry/cleo/commit/108f8214ef03107facafcba84379363768723fbd";><code>108f821</code></a>
 chore: Release 2.0.0</li>
   <li><a 
href="https://github.com/python-poetry/cleo/commit/78ae0300180f62b987989afc6c556134695527cf";><code>78ae030</code></a>
 Release 1.0.0</li>
   <li><a 
href="https://github.com/python-poetry/cleo/commit/b5b9a04d2caf58bf7cf94eb7ae4a1ebbe60ea455";><code>b5b9a04</code></a>
 Change regex string to less permissive one</li>
   <li><a 
href="https://github.com/python-poetry/cleo/commit/9ebf24fa4f8e6065765a4d48f87cb7a4d826dd95";><code>9ebf24f</code></a>
 Recreate lock</li>
   <li><a 
href="https://github.com/python-poetry/cleo/commit/675ec7e1d89aa65ce6dbca0938a89b4788db1045";><code>675ec7e</code></a>
 Refactor exceptions into errors as per PEP8 guidelines</li>
   <li><a 
href="https://github.com/python-poetry/cleo/commit/7d3623b719470dfbadf34c3919ed649357438021";><code>7d3623b</code></a>
 [pre-commit.ci] pre-commit autoupdate</li>
   <li><a 
href="https://github.com/python-poetry/cleo/commit/f760a59f241c5e396180b6d28027e4998d89fab9";><code>f760a59</code></a>
 removal(tox): remove unused tox</li>
   <li><a 
href="https://github.com/python-poetry/cleo/commit/d338ef775cc1436fc7b60cb31520914f9f76d6ca";><code>d338ef7</code></a>
 chore(mypy): bump mypy version (<a 
href="https://redirect.github.com/python-poetry/cleo/issues/282";>#282</a>)</li>
   <li><a 
href="https://github.com/python-poetry/cleo/commit/7af3362edff8faf8babf5bb6dc5b00510d266283";><code>7af3362</code></a>
 chore(pre-commit): update flake8 plugins (<a 
href="https://redirect.github.com/python-poetry/cleo/issues/280";>#280</a>)</li>
   <li><a 
href="https://github.com/python-poetry/cleo/commit/2efa20ec44bbc760d7ccd78a446e570b621798bd";><code>2efa20e</code></a>
 chore: add maintainers to pyproject.toml (<a 
href="https://redirect.github.com/python-poetry/cleo/issues/278";>#278</a>)</li>
   <li>Additional commits viewable in <a 
href="https://github.com/python-poetry/cleo/compare/0.8.1...2.0.0";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=cleo&package-manager=pip&previous-version=0.8.1&new-version=2.0.0)](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 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)
   You can disable automated security fix PRs for this repo from the [Security 
Alerts page](https://github.com/apache/tvm/network/alerts).
   
   </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]

Reply via email to