build(deps): bump the test-and-lint-dependencies group with 2 updates

[dependabot]

Bumps the test-and-lint-dependencies group with 2 updates: coverage and zizmor.

Updates coverage from 7.10.7 to 7.13.1

Changelog

Sourced from coverage's changelog.

Version 7.13.1 — 2025-12-28

• Added: the JSON report now includes a "start_line" key for function and class regions, indicating the first line of the region in the source. Closes issue 2110_.

• Added: The debug data command now takes file names as arguments on the command line, so you can inspect specific data files without needing to set the COVERAGE_FILE environment variable.

• Fix: the JSON report used to report module docstrings as executed lines, which no other report did, as described in issue 2105_. This is now fixed, thanks to Jianrong Zhao.

• Fix: coverage.py uses a more disciplined approach to detecting where third-party code is installed, and avoids measuring it. This shouldn't change any behavior. If you find that it does, please get in touch.

• Performance: data files that will be combined now record their hash as part of the file name. This lets us skip duplicate data more quickly, speeding the combining step.

• Docs: added a section explaining more about what is considered a missing branch and how it is reported: :ref:branch_explain, as requested in issue 1597. Thanks to Ayisha Mohammed <pull 2092_>.

• Tests: the test suite misunderstood what core was being tested if COVERAGE_CORE wasn't set on 3.14+. This is now fixed, closing issue 2109_.

.. _issue 1597: coveragepy/coveragepy#1597 .. _pull 2092: coveragepy/coveragepy#2092 .. _issue 2105: coveragepy/coveragepy#2105 .. _issue 2109: coveragepy/coveragepy#2109 .. _issue 2110: coveragepy/coveragepy#2110

.. _changes_7-13-0:

Version 7.13.0 — 2025-12-08

• Feature: coverage.py now supports :file:.coveragerc.toml configuration files. These files use TOML syntax and take priority over :file:pyproject.toml but lower priority than :file:.coveragerc files. Closes issue 1643_ thanks to Olena Yefymenko <pull 1952_>_.

• Fix: we now include a permanent .pth file which is installed with the code, fixing issue 2084_. In 7.12.1b1 this was done incorrectly: it didn't work when using the source wheel (py3-none-any). This is now fixed. Thanks,

... (truncated)

Commits

• a6afdc3 docs: sample HTML for 7.13.1
• a497081 docs: prep for 7.13.1
• e992033 docs: polish up CHANGES
• 18bba6e chore: bump the action-dependencies group with 4 updates (#2111)
• 80fb808 refactor: (?x:...) lets us use re.VERBOSE even when combining later
• cc272bd docs: leave a comment so we'll find this when 3.12 is the minimum
• 70d007d types: be explicit
• a2c1940 types: fully import modules that will be patched
• 57b975d types: explicit Protocol inheritance permits changing parameter names
• 63ec12d types: clarify that morfs arguments can be a single morf
• Additional commits viewable in compare view

Updates zizmor from 1.16.3 to 1.19.0

Release notes

Sourced from zizmor's releases.

v1.19.0

New Features 🌈🔗

• New audit: archived-uses detects usages of archived repositories in uses: clauses (#1411)

Enhancements 🌱🔗

• The use-trusted-publishing audit now detects additional publishing command patterns, including common "wrapped" patterns like bundle exec gem publish (#1394)

• zizmor now produces better error messages on a handful of error cases involving invalid input files. Specifically, a subset of syntax and schema errors now produce more detailed and actionable error messages (#1396)

• The use-trusted-publishing audit now detects additional publishing command patterns, including uv run ..., uvx ..., and poetry publish (#1402)

• zizmor now produces more useful and less ambiguous spans for many findings, particularly those from the anonymous-definition audit (#1416)

• zizmor now discovers configuration files named zizmor.yaml, in addition to zizmor.yml (#1431)

• zizmor now produces a more useful error message when input collection yields no inputs (#1439)

• The --render-links flag now allows users to control zizmor's OSC 8 terminal link rendering behavior. This is particularly useful in environments that advertise themselves as terminals but fail to correctly render or ignore OSC 8 links (#1454)

Performance Improvements 🚄🔗

• The [impostor-commit] audit is now significantly faster on true positives, making true positive detection virtually as fast as true negative detection. In practice, true positive runs are over 100 times faster than before (#1429)

Bug Fixes 🐛🔗

• Fixed a bug where the obfuscation audit would crash if it encountered a CMD shell that was defined outside of the current step block (i.e. as a job or workflow default) (#1418)

• Fixed a bug where the opentofu ecosystem was not recognized in Dependabot configuration files (#1452)

• --color=always no longer implies --render-links=always, as some environments (like GitHub Actions) support ANSI color codes but fail to handle OSC escapes gracefully (#1454)

v1.18.0

Enhancements 🌱🔗

• The use-trusted-publishing audit now detects NuGet publishing commands (#1369)

• The dependabot-cooldown audit now flags cooldown periods of less than 7 days by default (#1375)

• The dependabot-cooldown audit can now be configured with a custom minimum cooldown period via rules.dependabot-cooldown.config.days (#1377)

• zizmor now produces slightly more useful error messages when the user supplies an invalid configuration for the forbidden-uses audit (#1381)

Bug Fixes 🐛🔗

• Fixed additional edge cases where auto-fixed would fail to preserve a document's final newline (#1372)

v1.18.0-rc3

No release notes provided.

... (truncated)

Changelog

Sourced from zizmor's changelog.

1.19.0

New Features 🌈

• New audit: [archived-uses] detects usages of archived repositories in #!yaml uses: clauses (#1411)

Enhancements 🌱

• The [use-trusted-publishing] audit now detects additional publishing command patterns, including common "wrapped" patterns like bundle exec gem publish (#1394)

• zizmor now produces better error messages on a handful of error cases involving invalid input files. Specifically, a subset of syntax and schema errors now produce more detailed and actionable error messages (#1396)

• The [use-trusted-publishing] audit now detects additional publishing command patterns, including uv run ..., uvx ..., and poetry publish (#1402)

• zizmor now produces more useful and less ambiguous spans for many findings, particularly those from the [anonymous-definition] audit (#1416)

• zizmor now discovers configuration files named zizmor.yaml, in addition to zizmor.yml (#1431)

• zizmor now produces a more useful error message when input collection yields no inputs (#1439)

• The --render-links flag now allows users to control zizmor's OSC 8 terminal link rendering behavior. This is particularly useful in environments that advertise themselves as terminals but fail to correctly render or ignore OSC 8 links (#1454)

Performance Improvements 🚄

• The [impostor-commit] audit is now significantly faster on true positives, making true positive detection virtually as fast as true negative detection. In practice, true positive runs are over 100 times faster than before (#1429)

Bug Fixes 🐛

• Fixed a bug where the [obfuscation] audit would crash if it encountered a CMD shell that was defined outside of the current step block (i.e. as a job or workflow default) (#1418)

• Fixed a bug where the opentofu ecosystem was not recognized in Dependabot configuration files (#1452)

... (truncated)

Commits

• a5e304f Prep zizmor 1.19.0 (#1458)
• 2942f11 Bump all tree-sitter dependent crates (#1457)
• 9d61a10 Bump yamlpath to 0.30.0 (#1456)
• de6f9d6 ci: add plain presentation test (#1454)
• cc76e2b chore: bump github-actions-models to 0.42.0 (#1453)
• 7e1c93b fix: add OpenTofu to Dependabot package ecosystems (#1452)
• 081f844 docs: bump trophies (#1450)
• abdfe5d docs: bump trophies (#1449)
• 32d6831 chore(deps): bump tower-lsp-server from 0.22.1 to 0.23.0 in the cargo group (...
• eafa9e4 chore(deps): bump actions/checkout in the github-actions group (#1448)
• 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 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[jku]

We sohuld start running tests in python >= 3.10 so we can upgrade coverage and zizmor: 3.9 is EOL

[jku]

@dependabot rebase