build(deps-dev): bump the patch-and-minor group with 3 updates

[dependabot]

Bumps the patch-and-minor group with 3 updates: tox, coverage and boto3.

Updates tox from 4.60.1 to 4.61.2

Release notes

Sourced from tox's releases.

v4.61.2

What's Changed

• chore: add license-files, remove licence classifier (PEP 639) by @​mwtoews in tox-dev/tox#4052
• 🐛 fix(config): stop splitting factor names that look like ranges by @​MohammedAlkindi in tox-dev/tox#4053
• 📝 docs(config): cover the keys that had no reference entry by @​gaborbernat in tox-dev/tox#4056
• 📝 docs(config): document how factors work by @​gaborbernat in tox-dev/tox#4055
• 📝 docs: name the actor in the factor and schema prose by @​gaborbernat in tox-dev/tox#4057

New Contributors

• @​mwtoews made their first contribution in tox-dev/tox#4052

Full Changelog: tox-dev/tox@4.61.1...4.61.2

v4.61.1

What's Changed

• 🐛 fix(schema): declare prefix in the labeled factor group's not clause by @​gaborbernat in tox-dev/tox#4051

Full Changelog: tox-dev/tox@4.61.0...4.61.1

v4.61.0

What's Changed

• docs: fix dead virtualenv discovery link in explanation.rst by @​CAOShurong in tox-dev/tox#4042
• Replace deprecated load_module in docs conf by @​gaborbernat in tox-dev/tox#4043
• ✨ feat(toml): allow labeling a range factor group by @​gaborbernat in tox-dev/tox#4049
• 🐛 fix(config): substitute inside override values by @​gaborbernat in tox-dev/tox#4048
• ✨ feat(toml): declare factor group defaults and per-run overrides by @​gaborbernat in tox-dev/tox#4050

Full Changelog: tox-dev/tox@4.60.1...4.61.0

Changelog

Sourced from tox's changelog.

Bug fixes - 4.61.2

• tox now expands a generative digit range only where a factor starts, so an environment such as py313-django4-2 keeps its name rather than becoming py313-django4, 3 and 2 - by :user:MohammedAlkindi. (:issue:4053)

Improved documentation - 4.61.2

• Document how factors work in one place, covering what a factor is, the characters tox accepts in one, the platform and architecture factors that apply to conditions without appearing in a name, and how selecting by factor differs from selecting by name - by :user:gaborbernat. (:issue:4055)
• Give a reference entry to the configuration keys that had none. interrupt_post_commands runs commands_post after an interrupt, and config_file_path, host_python, home and tox_root_name are constants a configuration can substitute - by :user:gaborbernat. (:issue:4056)

Contributor-facing changes - 4.61.2

• Declare license metadata per PEP 639, adding license-files and dropping the license classifier in pyproject.toml - by :user:mwtoews. (:issue:4052)

---

v4.61.1 (2026-08-28)

---

Bug fixes - 4.61.1

• Publish a JSON Schema that compiles under SchemaStore's validator again, so editors pick up the configuration keys added since 4.56 - by :user:gaborbernat. (:issue:4051)

Contributor-facing changes - 4.61.1

• Check tox's JSON Schema with SchemaStore's own validator on every pull request that changes it, and again before the release sync opens a pull request there - by :user:gaborbernat. (:issue:4051)

---

v4.61.0 (2026-08-28)

---

Features - 4.61.0

• A labeled factor group can now declare a default for {factor:label} to fall back on when no factor of that group is active in the environment name. Setting TOX_FACTOR_<label> resolves that label to a given value for a single run - by :user:gaborbernat. (:issue:4045)
• A factor range now takes a label when you nest it under one, as in factors = [{ py_version = { prefix = "3.", start = 12, stop = 14 } }], which makes {factor:py_version} available for ranges - by :user:gaborbernat.

... (truncated)

Commits

• 44fc6ac release 4.61.2
• e28d9cf 📝 docs: name the actor in the factor and schema prose (#4057)
• c808c2d [pre-commit.ci] pre-commit autoupdate (#4054)
• 3aa0b69 📝 docs(config): document how factors work (#4055)
• 12b4270 📝 docs(config): cover the keys that had no reference entry (#4056)
• f31ebed 🐛 fix(config): stop splitting factor names that look like ranges (#4053)
• 96e2d71 chore: add license-files, remove licence classifier (PEP 639) (#4052)
• c8c010a release 4.61.1
• cd8c1fa 🐛 fix(schema): declare prefix in the labeled factor group's not clause (#4051)
• aa8f46c release 4.61.0
• Additional commits viewable in compare view

Updates coverage from 7.15.4 to 7.16.0

Release notes

Sourced from coverage's releases.

7.16.0

Version 7.16.0 — 2026-08-28

• When combining files, now path separator slashes will automatically be converted to the local file system style. This makes it less necessary to define [paths] configuration to combine data across operating systems. Fixes issue 2266.
• The Coverage.switch_context() method now returns the previous context.
• Fix: previously, a [paths] pattern would be replaced everywhere in a file path when it was only meant to be replaced once, in the leading portion of the path. This is now fixed, in pull 2268.
• Fixes to validation of options and configuration settings:
  • Negative precision settings now always cause useful error messages (pull 2261).
  • An invalid regex in the --contexts option (or the [report] contexts setting) reported a confusing “Couldn’t use data file …: user-defined function raised exception” error. Now it raises a proper configuration error naming the bad regex, like other regex settings do (pull 2262).
  • Non-string values in TOML configuration settings now produce a helpful error message instead of a traceback. This affects list settings whose elements aren’t strings (like omit, exclude_lines, or a [paths] entry), file settings like data_file, and any wrong-typed value in the [paths] section (pull 2263).
  • coverage run refuses run-affecting command-line options like --branch alongside --concurrency=multiprocessing, since they can’t reach the subprocesses. The check only recognized multiprocessing as the entire option value, so --concurrency=multiprocessing,thread slipped through and failed later with “Can’t combine statement coverage data with branch data”. Each named concurrency library is now properly considered (pull 2270).
• Fix: coverage annotate -d DIR raised an AssertionError if any measured file had an extension other than .py, such as a .pyw file on Windows. The original extension is now restored on the annotated copy (pull 2265).

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

Changelog

Sourced from coverage's changelog.

Version 7.16.0 — 2026-08-28

• When combining files, now path separator slashes will automatically be converted to the local file system style. This makes it less necessary to define [paths] configuration to combine data across operating systems. Fixes issue 2266_.

• The :meth:.Coverage.switch_context method now returns the previous context.

• Fix: previously, a [paths] pattern would be replaced everywhere in a file path when it was only meant to be replaced once, in the leading portion of the path. This is now fixed, in pull 2268_.

• Fixes to validation of options and configuration settings:

  • Negative precision settings now always cause useful error messages (pull 2261_).

  • An invalid regex in the --contexts option (or the [report] contexts setting) reported a confusing "Couldn't use data file ...: user-defined function raised exception" error. Now it raises a proper configuration error naming the bad regex, like other regex settings do (pull 2262_).

  • Non-string values in TOML configuration settings now produce a helpful error message instead of a traceback. This affects list settings whose elements aren't strings (like omit, exclude_lines, or a [paths] entry), file settings like data_file, and any wrong-typed value in the [paths] section (pull 2263_).

  • coverage run refuses run-affecting command-line options like --branch alongside --concurrency=multiprocessing, since they can't reach the subprocesses. The check only recognized multiprocessing as the entire option value, so --concurrency=multiprocessing,thread slipped through and failed later with "Can't combine statement coverage data with branch data". Each named concurrency library is now properly considered (pull 2270_).

• Fix: coverage annotate -d DIR raised an AssertionError if any measured file had an extension other than .py, such as a .pyw file on Windows. The original extension is now restored on the annotated copy (pull 2265_).

.. _pull 2261: coveragepy/coveragepy#2261 .. _pull 2262: coveragepy/coveragepy#2262 .. _pull 2263: coveragepy/coveragepy#2263 .. _pull 2265: coveragepy/coveragepy#2265 .. _issue 2266: coveragepy/coveragepy#2266 .. _pull 2268: coveragepy/coveragepy#2268

... (truncated)

Commits

• 3e9fc16 docs: prep for 7.16.0
• 38be8d1 build: control check-manifest explicitly
• 8eb1266 docs(build): no longer commit sample_html
• 1a8b3fa docs: remove sample_html
• aeaa79b docs: linklint is now sphinx-linklint
• d5eaf3f test: a branchless way to re-add extensions
• 57e52fd docs: adjust CHANGES for #2270
• b9d304d fix: check for multiprocessing in a --concurrency list (#2270)
• a6ef928 chore: make upgrade
• 070461f chore: bump the action-dependencies group with 4 updates (#2271)
• Additional commits viewable in compare view

Updates boto3 from 1.43.83 to 1.43.84

Commits

• ad412bb Merge branch 'release-1.43.84'
• c5da11c Bumping version to 1.43.84
• 706ed7e Add changelog entries from botocore
• 945550b Merge branch 'release-1.43.83' into develop
• See full diff 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