Bump coverage from 7.11.0 to 7.11.3 (#61)

Bumps [coverage](https://github.com/coveragepy/coveragepy) from 7.11.0
to 7.11.3.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/coveragepy/coveragepy/releases">coverage's
releases</a>.</em></p>
<blockquote>
<h2>7.11.3</h2>
<h2>Version 7.11.3 — 2025-11-09</h2>
<ul>
<li>
<p>Fix: the 7.11.1 changes meant that conflicts between a requested
measurement core and other settings would raise an error. This was a
breaking change from previous behavior, as reported in <a
href="https://redirect.github.com/coveragepy/coveragepy/issues/2076">issue
2076</a> and <a
href="https://redirect.github.com/coveragepy/coveragepy/issues/2078">issue
2078</a>.</p>
<p>The previous behavior has been restored: when the requested core
conflicts with other settings, another core is used instead, and a
warning is issued.</p>
</li>
<li>
<p>For contributors: the repo has moved from Ned’s <a
href="https://github.com/nedbat">nedbat GitHub account</a> to the <a
href="https://github.com/coveragepy">coveragepy GitHub organization</a>.
The default branch has changed from master to main.</p>
</li>
</ul>
<p>:arrow_right:  PyPI page: <a
href="https://pypi.org/project/coverage/7.11.3">coverage 7.11.3</a>.
:arrow_right:  To install: <code>python3 -m pip install
coverage==7.11.3</code></p>
<h2>7.11.2</h2>
<h2>Version 7.11.2 — 2025-11-08</h2>
<ul>
<li>Fix: using the “sysmon” measurement core in 7.11.1, if Python code
was claimed to come from a non-Python file, a <code>NotPython</code>
exception could be raised. This could happen for example with Jinja
templates compiled to Python, as reported in <a
href="https://redirect.github.com/coveragepy/coveragepy/issues/2077">issue
2077</a>. This is now fixed.</li>
<li>Doc: corrected the first entry in the 7.11.1 changelog.</li>
</ul>
<p>:arrow_right:  PyPI page: <a
href="https://pypi.org/project/coverage/7.11.2">coverage 7.11.2</a>.
:arrow_right:  To install: <code>python3 -m pip install
coverage==7.11.2</code></p>
<h2>7.11.1</h2>
<h2>Version 7.11.1 — 2025-11-07</h2>
<ul>
<li>Fix: some chanages to details of how the measurement core is chosen,
and how conflicting settings are handled. The “sysmon” core cannot be
used with some conurrency settings, with dynamic context, and in Python
3.12/3.13, with branch measurement.
<ul>
<li>If the core is not specified and defaults to “sysmon” (Python
3.14+), but other settings conflict with sysmon, then the “ctrace” core
will be used instead with no warning. For concurrency conflicts, this
used to produce an error, as described in <a
href="https://redirect.github.com/coveragepy/coveragepy/issues/2064">issue
2064</a>.</li>
<li>If the “sysmon” core is explicitly requested in your configuration,
but other settings conflict, an error is now raised. This used to
produce a warning.</li>
</ul>
</li>
<li>Fix: some multi-line case clauses or for loops (and probably other
constructs) could cause incorrect claims of missing branches with the
sys.monitoring core, as described in <a
href="https://redirect.github.com/coveragepy/coveragepy/issues/2070">issue
2070</a>. This is now fixed.</li>
<li>Fix: when running in pytest under coverage, a
<code>breakpoint()</code> would stop in the wrong frame, one level down
from where it should, as described in <a
href="https://redirect.github.com/coveragepy/coveragepy/issues/1420">issue
1420</a>. This was due to a coverage change in v6.4.1 that seemed to
give a slight performance improvement, but I couldn’t reproduce the
performance gain, so it’s been reverted, fixing the debugger
problem.</li>
<li>A new debug option <code>--debug=core</code> shows which core is in
use and why.</li>
<li>Split <code>sqlite</code> debugging information out of the
<code>sys</code> <a
href="https://github.com/coveragepy/coveragepy/blob/HEAD/commands/cmd_debug.rst#cmd-debug">coverage
debug</a> and <a
href="https://github.com/coveragepy/coveragepy/blob/HEAD/commands/cmd_debug.rst#cmd-run-debug">--debug
option</a> options since it’s bulky and not very useful.</li>
<li>Updated the <a
href="https://coverage.readthedocs.io/en/latest/howitworks.html#howitworks">How
coverage.py works</a> page to better describe the three different
measurement cores.</li>
</ul>
<p>:arrow_right:  PyPI page: <a
href="https://pypi.org/project/coverage/7.11.1">coverage 7.11.1</a>.
:arrow_right:  To install: <code>python3 -m pip install
coverage==7.11.1</code></p>
<h2>7.11.1</h2>
<h2>Version 7.11.1 — 2025-11-07</h2>
<ul>
<li>Fix: some chanages to details of how the measurement core is chosen,
and how conflicting settings are handled. The “sysmon” core cannot be
used with some conurrency settings, with dynamic context, and in Python
3.12/3.13, with branch measurement.
<ul>
<li>If the core is not specified and defaults to “sysmon” (Python
3.14+), but other settings conflict with sysmon, then the “ctrace” core
will be used instead with no warning. For concurrency conflicts, this
used to produce an error, as described in <a
href="https://redirect.github.com/coveragepy/coveragepy/issues/2064">issue
2064</a>.</li>
<li>If the “sysmon” core is explicitly requested in your configuration,
but other settings conflict, an error is now raised. This used to
produce a warning.</li>
</ul>
</li>
<li>Fix: some multi-line case clauses or for loops (and probably other
constructs) could cause incorrect claims of missing branches with the
sys.monitoring core, as described in <a
href="https://redirect.github.com/coveragepy/coveragepy/issues/2070">issue
2070</a>. This is now fixed.</li>
<li>Fix: when running in pytest under coverage, a
<code>breakpoint()</code> would stop in the wrong frame, one level down
from where it should, as described in <a
href="https://redirect.github.com/coveragepy/coveragepy/issues/1420">issue
1420</a>. This was due to a coverage change in v6.4.1 that seemed to
give a slight performance improvement, but I couldn’t reproduce the
performance gain, so it’s been reverted, fixing the debugger
problem.</li>
<li>A new debug option <code>--debug=core</code> shows which core is in
use and why.</li>
<li>Split <code>sqlite</code> debugging information out of the
<code>sys</code> <a
href="https://github.com/coveragepy/coveragepy/blob/HEAD/commands/cmd_debug.rst#cmd-debug">coverage
debug</a> and <a
href="https://github.com/coveragepy/coveragepy/blob/HEAD/commands/cmd_debug.rst#cmd-run-debug">--debug
option</a> options since it’s bulky and not very useful.</li>
<li>Updated the <a
href="https://coverage.readthedocs.io/en/latest/howitworks.html#howitworks">How
coverage.py works</a> page to better describe the three different
measurement cores.</li>
</ul>
<p>:arrow_right:  PyPI page: <a
href="https://pypi.org/project/coverage/7.11.1">coverage 7.11.1</a>.
:arrow_right:  To install: <code>python3 -m pip install
coverage==7.11.1</code></p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/coveragepy/coveragepy/blob/main/CHANGES.rst">coverage's
changelog</a>.</em></p>
<blockquote>
<h2>Version 7.11.3 — 2025-11-09</h2>
<ul>
<li>
<p>Fix: the 7.11.1 changes meant that conflicts between a requested
measurement
core and other settings would raise an error. This was a breaking change
from
previous behavior, as reported in <code>issue 2076</code>_ and
<code>issue 2078</code>_.</p>
<p>The previous behavior has been restored: when the requested core
conflicts
with other settings, another core is used instead, and a warning is
issued.</p>
</li>
<li>
<p>For contributors: the repo has moved from Ned's <code>nedbat GitHub
account</code>_ to
the <code>coveragepy GitHub organization</code>_. The default branch has
changed from
master to main.</p>
</li>
</ul>
<p>.. _issue 2076: <a
href="https://redirect.github.com/coveragepy/coveragepy/issues/2076">coveragepy/coveragepy#2076</a>
.. _issue 2078: <a
href="https://redirect.github.com/coveragepy/coveragepy/issues/2078">coveragepy/coveragepy#2078</a>
.. _nedbat GitHub account: <a
href="https://github.com/nedbat">https://github.com/nedbat</a>
.. _coveragepy GitHub organization: <a
href="https://github.com/coveragepy">https://github.com/coveragepy</a></p>
<p>.. _changes_7-11-2:</p>
<h2>Version 7.11.2 — 2025-11-08</h2>
<ul>
<li>
<p>Fix: using the &quot;sysmon&quot; measurement core in 7.11.1, if
Python code was
claimed to come from a non-Python file, a <code>NotPython</code>
exception could be
raised. This could happen for example with Jinja templates compiled to
Python, as reported in <code>issue 2077</code>_. This is now fixed.</p>
</li>
<li>
<p>Doc: corrected the first entry in the 7.11.1 changelog.</p>
</li>
</ul>
<p>.. _issue 2077: <a
href="https://redirect.github.com/coveragepy/coveragepy/issues/2077">coveragepy/coveragepy#2077</a></p>
<p>.. _changes_7-11-1:</p>
<h2>Version 7.11.1 — 2025-11-07</h2>
<ul>
<li>
<p>Fix: some chanages to details of how the measurement core is chosen,
and how
conflicting settings are handled. The &quot;sysmon&quot; core cannot be
used with some
conurrency settings, with dynamic context, and in Python 3.12/3.13, with
branch measurement.</p>
<ul>
<li>If the core is not specified and defaults to &quot;sysmon&quot;
(Python 3.14+), but
other settings conflict with sysmon, then the &quot;ctrace&quot; core
will be used
instead with no warning. For concurrency conflicts, this used to produce
an
error, as described in <code>issue 2064</code>_.</li>
</ul>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/coveragepy/coveragepy/commit/8bb1230de21cd8e3ffd4f7577d93b2406e2b8f9c"><code>8bb1230</code></a>
docs: remove duplicate entry in the changelog</li>
<li><a
href="https://github.com/coveragepy/coveragepy/commit/06c493cdfe0785fc67d538ed348d2262159a7ed5"><code>06c493c</code></a>
docs: sample HTML for 7.11.3</li>
<li><a
href="https://github.com/coveragepy/coveragepy/commit/0823a70f28111290cbe5e56a95c860f5a3aa30f1"><code>0823a70</code></a>
docs: prep for 7.11.3</li>
<li><a
href="https://github.com/coveragepy/coveragepy/commit/843479261fd9cb10ab739f50406a36ed4024ec92"><code>8434792</code></a>
fix: sysmon conflicts no longer cause errors</li>
<li><a
href="https://github.com/coveragepy/coveragepy/commit/1f211841cfe5756b322301dcca446e5398f0d8ea"><code>1f21184</code></a>
chore: bump docker/setup-qemu-action in the action-dependencies group
(<a
href="https://redirect.github.com/coveragepy/coveragepy/issues/2080">#2080</a>)</li>
<li><a
href="https://github.com/coveragepy/coveragepy/commit/bd61620d805ec5d178722ec9aae5466b7514f56f"><code>bd61620</code></a>
docs: django_coverage_plugin moved</li>
<li><a
href="https://github.com/coveragepy/coveragepy/commit/1bd73f1aa418804f78f4c83e96c9d675339c50b4"><code>1bd73f1</code></a>
build: nedbat/coverage-reports moved to coveragepy/metacov-reports</li>
<li><a
href="https://github.com/coveragepy/coveragepy/commit/b54131fd090613b5f251342d9e7ee356026bf8b8"><code>b54131f</code></a>
docs: moved to coveragepy, master-&gt;main</li>
<li><a
href="https://github.com/coveragepy/coveragepy/commit/f2d740fdb856dfae8aff4634ece15e436f7d9e9a"><code>f2d740f</code></a>
build: change more github urls to the coveragepy org</li>
<li><a
href="https://github.com/coveragepy/coveragepy/commit/776f313f5415bc95ea736f6486634c3f9d0b96f4"><code>776f313</code></a>
docs: issue and pr references moved to coveragepy org</li>
<li>Additional commits viewable in <a
href="https://github.com/coveragepy/coveragepy/compare/7.11.0...7.11.3">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=coverage&package-manager=uv&previous-version=7.11.0&new-version=7.11.3)](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>

Author: dependabot[bot]

pyproject.toml

@@ -54,7 +54,7 @@ dev = [
 ]
 test = [
     "pytest==9.0.0",
-    "coverage==7.11.0",
+    "coverage==7.11.3",
     "diff-cover==9.7.1",
     "pytest-cov==7.0.0",
     "pytest-randomly==4.0.1",