Bump the prod-dependencies group across 1 directory with 2 updates

[dependabot]

Bumps the prod-dependencies group with 2 updates in the / directory: pytest-cov and copier.

Updates pytest-cov from 7.0.0 to 7.1.0

Changelog

Sourced from pytest-cov's changelog.

7.1.0 (2026-03-21)

• Fixed total coverage computation to always be consistent, regardless of reporting settings. Previously some reports could produce different total counts, and consequently can make --cov-fail-under behave different depending on reporting options. See [#641](https://github.com/pytest-dev/pytest-cov/issues/641) <https://github.com/pytest-dev/pytest-cov/issues/641>_.

• Improve handling of ResourceWarning from sqlite3.

  The plugin adds warning filter for sqlite3 ResourceWarning unclosed database (since 6.2.0). It checks if there is already existing plugin for this message by comparing filter regular expression. When filter is specified on command line the message is escaped and does not match an expected message. A check for an escaped regular expression is added to handle this case.

  With this fix one can suppress ResourceWarning from sqlite3 from command line::

  pytest -W "ignore:unclosed database in <sqlite3.Connection object at:ResourceWarning" ...

• Various improvements to documentation. Contributed by Art Pelling in [#718](https://github.com/pytest-dev/pytest-cov/issues/718) <https://github.com/pytest-dev/pytest-cov/pull/718>_ and "vivodi" in [#738](https://github.com/pytest-dev/pytest-cov/issues/738) <https://github.com/pytest-dev/pytest-cov/pull/738>. Also closed [#736](https://github.com/pytest-dev/pytest-cov/issues/736) <https://github.com/pytest-dev/pytest-cov/issues/736>.

• Fixed some assertions in tests. Contributed by in Markéta Machová in [#722](https://github.com/pytest-dev/pytest-cov/issues/722) <https://github.com/pytest-dev/pytest-cov/pull/722>_.

• Removed unnecessary coverage configuration copying (meant as a backup because reporting commands had configuration side-effects before coverage 5.0).

Commits

• 66c8a52 Bump version: 7.0.0 → 7.1.0
• f707662 Make the examples use pypy 3.11.
• 6049a78 Make context test use the old ctracer (seems the new sysmon tracer behaves di...
• 8ebf20b Update changelog.
• 861d30e Remove the backup context manager - shouldn't be needed since coverage 5.0, ...
• fd4c956 Pass the precision on the nulled total (seems that there's some caching goion...
• 78c9c4e Only run the 3.9 on older deps.
• 4849a92 Punctuation.
• 197c35e Update changelog and hopefully I don't forget to publish release again :))
• 14dc1c9 Update examples to use 3.11 and make the adhoc layout example look a bit more...
• Additional commits viewable in compare view

Updates copier from 9.11.2 to 9.14.0

Release notes

Sourced from copier's releases.

v9.14.0 (2026-03-13)

Feat

• cli: add --answers-file flag to check-update command

Fix

• only warn about dirty template when checking out HEAD
• cli: show only supported flags in check-update command help output

v9.13.1 (2026-03-09)

Fix

• vcs: make Git version parsing robust to vendor-suffixed patch versions

v9.13.0 (2026-03-05)

Feat

• add CLI subcommand check-update to check for new template version (#2463)

Refactor

• cli: call public run_* functions instead of internal Worker.run_* methods

v9.12.0 (2026-02-21)

Feat

• add new settings API with minimal surface
• re-export Phase enum at package level

Fix

• updating: apply skip-if-exists patterns as gitignore-style at subproject root in update algorithm
• updating: anchor removed file paths to project root in update algorithm
• updating: normalize user-deleted paths before skip-if-exists pattern matching during updates

Refactor

• typing: use builtin types in public API signatures
• deprecate public settings module and its symbols
• replace **kwargs with explicit parameters in run_{copy,recopy,update} functions

v9.11.3 (2026-01-23)

Fix

• updating: include non-question answers when generating fresh copy of new template
• updating: ignore Git hooks on internal checkout before 3-way merging file with

... (truncated)

Changelog

Sourced from copier's changelog.

v9.14.0 (2026-03-13)

Feat

• cli: add --answers-file flag to check-update command

Fix

• only warn about dirty template when checking out HEAD
• cli: show only supported flags in check-update command help output

v9.13.1 (2026-03-09)

Fix

• vcs: make Git version parsing robust to vendor-suffixed patch versions

v9.13.0 (2026-03-05)

Feat

• add CLI subcommand check-update to check for new template version (#2463)

Refactor

• cli: call public run_* functions instead of internal Worker.run_* methods

v9.12.0 (2026-02-21)

Feat

• add new settings API with minimal surface
• re-export Phase enum at package level

Fix

• updating: apply skip-if-exists patterns as gitignore-style at subproject root in update algorithm
• updating: anchor removed file paths to project root in update algorithm
• updating: normalize user-deleted paths before skip-if-exists pattern matching during updates

Refactor

• typing: use builtin types in public API signatures
• deprecate public settings module and its symbols
• replace **kwargs with explicit parameters in run_{copy,recopy,update} functions

v9.11.3 (2026-01-23)

... (truncated)

Commits

• c90d3a6 bump: version 9.13.1 → 9.14.0
• 07d7f61 test(cli): snapshot help output for copy and update commands
• 7ac0ca4 feat(cli): add --answers-file flag to check-update command
• 4c419a8 fix: only warn about dirty template when checking out HEAD
• 4381df2 fix(cli): show only supported flags in check-update command help output
• 99dc1a0 bump: version 9.13.0 → 9.13.1
• 1ba971c fix(vcs): make Git version parsing robust to vendor-suffixed patch versions
• 128f000 build(deps): update dependency ruff to v0.15.5
• bcb5c02 docs: remove outdated note about updating multiselect choices via --data flag
• 9fc033e build(deps): update dependency platformdirs to v4.9.4
• 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 <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