Store the `openapi.json` of the backend in the repo and import it using
https://heyapi.dev/ to generate TypeScript types for the backend API
query params, responses, bodies.
Bumps [pyrefly](https://github.com/facebook/pyrefly) from 0.44.0 to
0.45.0.
<details>
<summary>Commits</summary>
<ul>
<li><a
href="93cacf99df"><code>93cacf9</code></a>
Update pyrefly version]</li>
<li><a
href="9ed447ce33"><code>9ed447c</code></a>
special-case numba.jit and numba.njit to preserve decorated function
signatures</li>
<li><a
href="495e7dcfaf"><code>495e7dc</code></a>
Remove Arc from HeavyTaskQueue</li>
<li><a
href="e34715c8b9"><code>e34715c</code></a>
Remove Arc from connection and lsp_queue</li>
<li><a
href="361ad739f1"><code>361ad73</code></a>
Borrow in server threads</li>
<li><a
href="f2482475e5"><code>f248247</code></a>
Run server threads in a thread scope</li>
<li><a
href="87cfca7e60"><code>87cfca7</code></a>
Stop listening for LSP requests after Exit notification</li>
<li><a
href="7f485246d8"><code>7f48524</code></a>
Move Pydantic lax mode into its own file</li>
<li><a
href="40759d7b44"><code>40759d7</code></a>
regression test for lazy class attr init</li>
<li><a
href="3f263a0470"><code>3f263a0</code></a>
Move suggest.rs into the pyrefly_util crate</li>
<li>Additional commits viewable in <a
href="https://github.com/facebook/pyrefly/compare/0.44.0...0.45.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 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)
</details>
---------
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Erik Vroon <erik.vroon@channable.com>
Updates the requirements on [ruff](https://github.com/astral-sh/ruff) to
permit the latest version.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/astral-sh/ruff/releases">ruff's
releases</a>.</em></p>
<blockquote>
<h2>0.11.0</h2>
<h2>Release Notes</h2>
<p>This is a follow-up to <a
href="https://github.com/astral-sh/ruff/releases/tag/0.10.0">release
0.10.0</a>. The <code>requires-python</code> inference changes were
unintentionally omitted from 0.10.0, and have been included here. This
release also includes stabilization of the preview behavior for
<code>PGH004</code>.</p>
<h3>Breaking changes</h3>
<ul>
<li>
<p><strong>Changes to how the Python version is inferred when a
<code>target-version</code> is not specified</strong> (<a
href="https://redirect.github.com/astral-sh/ruff/pull/16319">#16319</a>)</p>
<p>In previous versions of Ruff, you could specify your Python version
with:</p>
<ul>
<li>The <code>target-version</code> option in a <code>ruff.toml</code>
file or the <code>[tool.ruff]</code> section of a pyproject.toml
file.</li>
<li>The <code>project.requires-python</code> field in a
<code>pyproject.toml</code> file with a <code>[tool.ruff]</code>
section.</li>
</ul>
<p>These options worked well in most cases, and are still recommended
for fine control of the Python version. However, because of the way Ruff
discovers config files, <code>pyproject.toml</code> files without a
<code>[tool.ruff]</code> section would be ignored, including the
<code>requires-python</code> setting. Ruff would then use the default
Python version (3.9 as of this writing) instead, which is surprising
when you've attempted to request another version.</p>
<p>In v0.10, config discovery has been updated to address this
issue:</p>
<ul>
<li>If Ruff finds a <code>ruff.toml</code> file without a
<code>target-version</code>, it will check
for a <code>pyproject.toml</code> file in the same directory and respect
its
<code>requires-python</code> version, even if it does not contain a
<code>[tool.ruff]</code>
section.</li>
<li>If Ruff finds a user-level configuration, the
<code>requires-python</code> field of the closest
<code>pyproject.toml</code> in a parent directory will take
precedence.</li>
<li>If there is no config file (<code>ruff.toml</code>or
<code>pyproject.toml</code> with a
<code>[tool.ruff]</code> section) in the directory of the file being
checked, Ruff will
search for the closest <code>pyproject.toml</code> in the parent
directories and use its
<code>requires-python</code> setting.</li>
</ul>
</li>
</ul>
<h3>Stabilization</h3>
<p>The following behaviors have been stabilized:</p>
<ul>
<li><a
href="https://docs.astral.sh/ruff/rules/blanket-noqa/"><code>blanket-noqa</code></a>
(<code>PGH004</code>): Also detect blanked file-level noqa comments (and
not just line level comments).</li>
</ul>
<h3>Preview features</h3>
<ul>
<li>[syntax-errors] Tuple unpacking in <code>for</code> statement
iterator clause before Python 3.9 (<a
href="https://redirect.github.com/astral-sh/ruff/pull/16558">#16558</a>)</li>
</ul>
<h2>Install ruff 0.11.0</h2>
<h3>Install prebuilt binaries via shell script</h3>
<pre lang="sh"><code>curl --proto '=https' --tlsv1.2 -LsSf
https://github.com/astral-sh/ruff/releases/download/0.11.0/ruff-installer.sh
| sh
</code></pre>
<h3>Install prebuilt binaries via powershell script</h3>
<pre lang="sh"><code>powershell -ExecutionPolicy ByPass -c "irm
https://github.com/astral-sh/ruff/releases/download/0.11.0/ruff-installer.ps1
| iex"
</tr></table>
</code></pre>
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md">ruff's
changelog</a>.</em></p>
<blockquote>
<h2>0.11.0</h2>
<p>This is a follow-up to release 0.10.0. Because of a mistake in the
release process, the <code>requires-python</code> inference changes were
not included in that release. Ruff 0.11.0 now includes this change as
well as the stabilization of the preview behavior for
<code>PGH004</code>.</p>
<h3>Breaking changes</h3>
<ul>
<li>
<p><strong>Changes to how the Python version is inferred when a
<code>target-version</code> is not specified</strong> (<a
href="https://redirect.github.com/astral-sh/ruff/pull/16319">#16319</a>)</p>
<p>In previous versions of Ruff, you could specify your Python version
with:</p>
<ul>
<li>The <code>target-version</code> option in a <code>ruff.toml</code>
file or the <code>[tool.ruff]</code> section of a pyproject.toml
file.</li>
<li>The <code>project.requires-python</code> field in a
<code>pyproject.toml</code> file with a <code>[tool.ruff]</code>
section.</li>
</ul>
<p>These options worked well in most cases, and are still recommended
for fine control of the Python version. However, because of the way Ruff
discovers config files, <code>pyproject.toml</code> files without a
<code>[tool.ruff]</code> section would be ignored, including the
<code>requires-python</code> setting. Ruff would then use the default
Python version (3.9 as of this writing) instead, which is surprising
when you've attempted to request another version.</p>
<p>In v0.10, config discovery has been updated to address this
issue:</p>
<ul>
<li>If Ruff finds a <code>ruff.toml</code> file without a
<code>target-version</code>, it will check
for a <code>pyproject.toml</code> file in the same directory and respect
its
<code>requires-python</code> version, even if it does not contain a
<code>[tool.ruff]</code>
section.</li>
<li>If Ruff finds a user-level configuration, the
<code>requires-python</code> field of the closest
<code>pyproject.toml</code> in a parent directory will take
precedence.</li>
<li>If there is no config file (<code>ruff.toml</code>or
<code>pyproject.toml</code> with a
<code>[tool.ruff]</code> section) in the directory of the file being
checked, Ruff will
search for the closest <code>pyproject.toml</code> in the parent
directories and use its
<code>requires-python</code> setting.</li>
</ul>
</li>
</ul>
<h3>Stabilization</h3>
<p>The following behaviors have been stabilized:</p>
<ul>
<li><a
href="https://docs.astral.sh/ruff/rules/blanket-noqa/"><code>blanket-noqa</code></a>
(<code>PGH004</code>): Also detect blanked file-level noqa comments (and
not just line level comments).</li>
</ul>
<h3>Preview features</h3>
<ul>
<li>[syntax-errors] Tuple unpacking in <code>for</code> statement
iterator clause before Python 3.9 (<a
href="https://redirect.github.com/astral-sh/ruff/pull/16558">#16558</a>)</li>
</ul>
<h2>0.10.0</h2>
<p>Check out the <a href="https://astral.sh/blog/ruff-v0.10.0">blog
post</a> for a migration guide and overview of the changes!</p>
<h3>Breaking changes</h3>
<p>See also, the "Remapped rules" section which may result in
disabled rules.</p>
<ul>
<li>
<p><strong>Changes to how the Python version is inferred when a
<code>target-version</code> is not specified</strong> (<a
href="https://redirect.github.com/astral-sh/ruff/pull/16319">#16319</a>)</p>
<p>Because of a mistake in the release process, the
<code>requires-python</code> inference changes are not included in this
release and instead shipped as part of 0.11.0.
You can find a description of this change in the 0.11.0 section.</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="2cd25ef641"><code>2cd25ef</code></a>
Ruff 0.11.0 (<a
href="https://redirect.github.com/astral-sh/ruff/issues/16723">#16723</a>)</li>
<li><a
href="a22d206db2"><code>a22d206</code></a>
[red-knot] Preliminary tests for typing.Final (<a
href="https://redirect.github.com/astral-sh/ruff/issues/15917">#15917</a>)</li>
<li><a
href="270318c2e0"><code>270318c</code></a>
[red-knot] fix: improve type inference for binary ops on tuples (<a
href="https://redirect.github.com/astral-sh/ruff/issues/16725">#16725</a>)</li>
<li><a
href="d03b12e711"><code>d03b12e</code></a>
[red-knot] Assignments to attributes (<a
href="https://redirect.github.com/astral-sh/ruff/issues/16705">#16705</a>)</li>
<li><a
href="14c5ed5d7d"><code>14c5ed5</code></a>
[<code>pygrep-hooks</code>]: Detect file-level suppressions comments
without rul… (<a
href="https://redirect.github.com/astral-sh/ruff/issues/16720">#16720</a>)</li>
<li><a
href="595565015b"><code>5955650</code></a>
Fallback to requires-python in certain cases when target-version is not
found...</li>
<li><a
href="2382fe1f25"><code>2382fe1</code></a>
[syntax-errors] Tuple unpacking in <code>for</code> statement iterator
clause before Pyt...</li>
<li><a
href="27e9d1fe3e"><code>27e9d1f</code></a>
Ruff v0.10 Release (<a
href="https://redirect.github.com/astral-sh/ruff/issues/16708">#16708</a>)</li>
<li><a
href="acf35c55f8"><code>acf35c5</code></a>
Add new <code>noqa</code> specification to the docs (<a
href="https://redirect.github.com/astral-sh/ruff/issues/16703">#16703</a>)</li>
<li><a
href="b9b256209b"><code>b9b2562</code></a>
describe requires-python fallback in docs (<a
href="https://redirect.github.com/astral-sh/ruff/issues/16704">#16704</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/astral-sh/ruff/compare/0.9.1...0.11.0">compare
view</a></li>
</ul>
</details>
<br />
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)
</details>
---------
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Erik Vroon <erik.vroon@channable.com>
