Bump coverage from 7.14.1 to 7.15.2

[dependabot]

Bumps coverage from 7.14.1 to 7.15.2.

Release notes

Sourced from coverage's releases.

7.15.2

Version 7.15.2 — 2026-07-15

• Fix: one of the performance improvements in 7.15.1 (pull 2215) dramatically increased memory use during reporting for large projects. Now we use a different approach that is both faster and slimmer than 7.15.0. Fixes issue 2229.

➡️  PyPI page: coverage 7.15.2. :arrow_right:  To install: python3 -m pip install coverage==7.15.2

7.15.1

Version 7.15.1 — 2026-07-12

• Fix: in the HTML report with show_contexts enabled, a context label containing </script> (for example a parametrized pytest node id) could close the inline <script> element in a file page early, injecting markup. Context labels are now fully escaped. Thanks, Rajath Mohare.
• A number of performance improvements thanks to Paul Kehrer, in pull requests 2213, 2214, 2215, 2216, 2218, 2220, and 2221.

➡️  PyPI page: coverage 7.15.1. :arrow_right:  To install: python3 -m pip install coverage==7.15.1

7.15.0

Version 7.15.0 — 2026-07-02

• Since 7.14.0, reporting commands implicitly combine parallel data files. Now those commands have a new option --keep-combined to retain the data files after combining them instead of the default, which is to delete them. Finishes issue 2198.
• Fix: the LCOV report would incorrectly count excluded functions as uncovered, as described in issue 2205. This is now fixed thanks to Martin Kuntz Jacobsen.
• When running your program, coverage now correctly sets yourmodule.__spec__.loader as strongly recommended, avoiding the deprecation warning described in issue 2208. Thanks, A5rocks.
• Fix: with Python 3.10, running with the -I (isolated mode) option didn’t correctly omit the current directory from the module search path, as described in issue 2103. That is now fixed thanks to Ilia Sorokin.

➡️  PyPI page: coverage 7.15.0. :arrow_right:  To install: python3 -m pip install coverage==7.15.0

7.14.3

Version 7.14.3 — 2026-06-22

• Fix: the default ... exclusion rule now also matches function bodies whose closing return-type bracket is on its own line (for example, after a long -> dict[ ... ] annotation that a formatter has split over multiple lines). Closes issue 2185, thanks Mengjia Shang.
• Fix: On 3.13t, we incorrectly issued Couldn't import C tracer errors. We can’t import the C tracer because in 7.14.2 we stopped shipping compiled wheels for 3.13t. Thanks, Hugo van Kemenade.

➡️  PyPI page: coverage 7.14.3. :arrow_right:  To install: python3 -m pip install coverage==7.14.3

7.14.2

Version 7.14.2 — 2026-06-20

• Fix: some messages were being written to stdout, making coverage json -o - useless for capturing JSON output. Now messages are written to stderr, fixing issue 2197.
• Fix: CoverageData kept one SQLite connection per thread that recorded coverage, but never closed them when those threads terminated. On long runs with many short-lived threads this leaked one file descriptor per dead thread, eventually failing with OSError: [Errno 24] Too many open files. Connections belonging to terminated threads are now closed and dropped. Fixes issue 2192. Thanks, Matthew Lloyd.
• Fix: when using sys.monitoring, we were assuming we could use the COVERAGE_ID tool id. But other tools might also assume they could use that id. Pre-allocated ids don’t really make sense, so now we search for a usable one instead. Fixes issue 2187.
• Following the advice of cibuildwheel, we no longer distribute wheels for Python 3.13 free-threaded.

➡️  PyPI page: coverage 7.14.2. :arrow_right:  To install: python3 -m pip install coverage==7.14.2

Changelog

Sourced from coverage's changelog.

Version 7.15.2 — 2026-07-15

• Fix: one of the performance improvements in 7.15.1 (pull 2215) dramatically increased memory use during reporting for large projects. Now we use a different approach that is both faster and slimmer than 7.15.0. Fixes issue 2229_.

.. _issue 2229: coveragepy/coveragepy#2229

.. _changes_7-15-1:

Version 7.15.1 — 2026-07-12

• Fix: in the HTML report with show_contexts enabled, a context label containing </script> (for example a parametrized pytest node id) could close the inline <script> element in a file page early, injecting markup. Context labels are now fully escaped. Thanks, Rajath Mohare <pull 2224_>_.

• A number of performance improvements thanks to Paul Kehrer, in pull requests 2213 <pull 2213_>, 2214 <pull 2214_>, 2215 <pull 2215_>, 2216 <pull 2216_>, 2218 <pull 2218_>, 2220 <pull 2220_>, and 2221 <pull 2221_>_.

.. _pull 2213: coveragepy/coveragepy#2213 .. _pull 2214: coveragepy/coveragepy#2214 .. _pull 2215: coveragepy/coveragepy#2215 .. _pull 2216: coveragepy/coveragepy#2216 .. _pull 2218: coveragepy/coveragepy#2218 .. _pull 2220: coveragepy/coveragepy#2220 .. _pull 2221: coveragepy/coveragepy#2221 .. _pull 2224: coveragepy/coveragepy#2224

.. _changes_7-15-0:

Version 7.15.0 — 2026-07-02

• Since 7.14.0, reporting commands implicitly combine parallel data files. Now those commands have a new option --keep-combined to retain the data files after combining them instead of the default, which is to delete them. Finishes issue 2198_.

• Fix: the LCOV report would incorrectly count excluded functions as uncovered, as described in issue 2205. This is now fixed thanks to Martin Kuntz Jacobsen <pull 2206_>.

• When running your program, coverage now correctly sets

... (truncated)

Commits

• 50d8659 docs: sample HTML for 7.15.2
• b5eed20 docs: prep for 7.15.2
• 78cab6e fix: reduce memory use during reporting. #2229 (#2231)
• b4c1fda build: bump version to 7.15.2
• da63bed docs: sample HTML for 7.15.1
• bc35e64 docs: prep for 7.15.1
• 182b010 perf: resolve sysmon branch events lazily, one pair at a time (#2221)
• ee271ee perf: compute multiline maps cheaply in the sysmon core (#2220)
• 1441b96 chore: bump the action-dependencies group with 6 updates (#2225)
• dd80635 fix: escape context labels in html report inline script block (#2224)
• Additional commits viewable 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 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)

[github-actions]

📌 Esta mensagem está tanto em português quanto em inglês (mais abaixo) — assim todo mundo consegue acompanhar!
📌 This message is in both Portuguese and English (further down) — so everyone can follow along!

🇧🇷 Português

Oi! Muito obrigada por abrir esse pull request 💜

Por aqui, seguimos o padrão do Conventional Commits para os títulos das PRs.
Esse padrão ajuda a manter o histórico do projeto organizado e claro.

No seu caso, o título do PR precisa de um pequeno ajuste pra ficar dentro desse formato. Isso é super comum no começo, então suaveee!

👉 Um título válido geralmente começa com um prefixo como:

• build: para mudanças no sistema de build ou dependências externas
• chore: para tarefas de manutenção
• ci: para integrações contínuas
• docs: para mudanças na documentação
• feat: para novas funcionalidades
• fix: para correções de bugs
• perf: para melhorias de performance
• refactor: para melhorias internas no código
• revert: para reverter um commit anterior
• style: para mudanças de formatação
• test: para adição ou ajustes de testes

Exemplos de títulos que adoraríamos ver por aqui:

prefixo: mensagem descritiva

feat: permitir que o objeto de configuração fornecido estenda outras configurações

fix: corrige pequenos erros de digitação no código

Esses são só alguns exemplos — a documentação oficial tem mais opções e explicações.

Antes de seguir com o PR, dá uma olhadinha lá pra entender bem o padrão — isso vai te ajudar bastante nesta e em futuras contribuições também.

O título atual está assim (fora do padrão esperado):

No release type found in pull request title "Bump coverage from 7.14.1 to 7.15.2". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - build
 - chore
 - ci
 - docs
 - feat
 - fix
 - perf
 - refactor
 - revert
 - style
 - test

Qualquer dúvida, é só chamar por aqui! Estamos aqui para te ajudar!

🇬🇧 English

Hey there and thank you for opening this pull request! 💜

In this project, we follow the Conventional Commits specification for PR titles.
This helps keep the commit history organized and clean.

In your case, the PR title needs a small adjustment to match the expected format. Totally normal if this is your first time — no stress!

👉 A valid PR title usually starts with a prefix like:

• build: for build system or external dependency changes
• chore: for maintenance tasks
• ci: for continuous integration changes
• docs: for documentation updates
• feat: for new features
• fix: for bug fixes
• perf: for performance improvements
• refactor: for internal code improvements
• revert: for reverting a previous commit
• style: for formatting changes
• test: for test additions or changes

Examples of titles we'd love to see here:

prefix: descriptive message

feat: allow the provided config object to extend other configurations

fix: correct minor typos in the code

These are just a few examples — the official documentation has more options and great explanations.
Before continuing with the PR, we recommend reading it — it'll really help with this and future contributions.

💡 Here's the current title (which doesn't follow the expected format):

No release type found in pull request title "Bump coverage from 7.14.1 to 7.15.2". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - build
 - chore
 - ci
 - docs
 - feat
 - fix
 - perf
 - refactor
 - revert
 - style
 - test

Let us know if you need help updating it — we’re here to support you!