Bump the minor-patch group with 4 updates

[dependabot]

Bumps the minor-patch group with 4 updates: coverage, yamllint, responses and ruff.

Updates coverage from 7.6.12 to 7.7.0

Changelog

Sourced from coverage's changelog.

Version 7.7.0 — 2025-03-16

• The Coverage object has a new method, :meth:.Coverage.branch_stats for getting simple branch information for a module. Closes issue 1888_.

• The :class:Coverage constructor<.Coverage> now has a plugins parameter for passing in plugin objects directly, thanks to Alex Gaynor <pull 1919_>_.

• Many constant tests in if statements are now recognized as being optimized away. For example, previously if 13: would have been considered a branch with one path not taken. Now it is understood as always true and no coverage is missing.

• The experimental sys.monitoring support now works for branch coverage if you are using Python 3.14.0 alpha 6 or newer. This should reduce the overhead coverage.py imposes on your test suite. Set the environment variable COVERAGE_CORE=sysmon to try it out.

• Confirmed support for PyPy 3.11. Thanks Michał Górny.

.. _issue 1888: nedbat/coveragepy#1888 .. _pull 1919: nedbat/coveragepy#1919

.. _changes_7-6-12:

Commits

• 61dcf71 docs: sample HTML for 7.7.0
• 35a31c5 docs: prep for 7.7.0
• 8f6e006 docs: edit the changelog
• 33f12df feat: Coverage.branch_stats() #1888
• c4919cb lint: somehow these snuck through
• 7e9f2f2 perf(sysmon): silly mistake
• 1e99d28 perf(sysmon): improve speed
• c9908d7 test: benchmark improvements
• 0973f44 chore: bump the action-dependencies group with 2 updates (#1935)
• 824b3ba style: fix one change from updated pylint
• Additional commits viewable in compare view

Updates yamllint from 1.35.1 to 1.36.1

Changelog

Sourced from yamllint's changelog.

1.36.1 (2025-03-15)

• Publish PyPI releases using GitHub Actions workflows

1.36.0 (2025-03-11)

• Add support for Python 3.13, drop support for Python 3.8
• Rule key-ordering: add ignored-keys option
• Rule quoted-strings: fix only-when-needed and escaped special chars
• Fix TTY-related tests on Python 3.14
• Docs: fix import of yamllint.config rather than yamllint

Commits

• 27d05bd yamllint version 1.36.1
• a3e1325 CI: Publish PyPI releases using GitHub Actions workflows
• 1c3bbb2 CI: Rename the GitHub Actions workflow file tests.yaml
• d5b6c4a yamllint version 1.36.0
• dc214be Drop support for Python 3.8
• fb7fc98 quoted-strings: Fix crash with only-when-needed and escaped special characters
• 0695155 style: Apply ruff/flake8-pie rule PIE800
• d8f1d7c style: Apply ruff/refurb rule FURB188
• 2f87db8 key-ordering: Add ignored-keys option
• e427005 cli: Fix TTY test failing on Python 3.14
• Additional commits viewable in compare view

Updates responses from 0.25.6 to 0.25.7

Release notes

Sourced from responses's releases.

0.25.7

• Added support for python 3.13

Changelog

Sourced from responses's changelog.

0.25.7

• Added support for python 3.13

Commits

• 7fc249b release: 0.25.7
• ba45c5d Update CHANGES (#760)
• d663d65 added pull request template (#759)
• a9e8bee added support for Python 3.13 (#758)
• 489b847 Merge branch 'release/0.25.6'
• See full diff in compare view

Updates ruff from 0.9.10 to 0.11.0

Release notes

Sourced from ruff's releases.

0.11.0

Release Notes

This is a follow-up to release 0.10.0. The requires-python inference changes were unintentionally omitted from 0.10.0, and have been included here. This release also includes stabilization of the preview behavior for PGH004.

Breaking changes

• Changes to how the Python version is inferred when a target-version is not specified (#16319)

  In previous versions of Ruff, you could specify your Python version with:

  • The target-version option in a ruff.toml file or the [tool.ruff] section of a pyproject.toml file.
  • The project.requires-python field in a pyproject.toml file with a [tool.ruff] section.

  These options worked well in most cases, and are still recommended for fine control of the Python version. However, because of the way Ruff discovers config files, pyproject.toml files without a [tool.ruff] section would be ignored, including the requires-python setting. Ruff would then use the default Python version (3.9 as of this writing) instead, which is surprising when you've attempted to request another version.

  In v0.10, config discovery has been updated to address this issue:

  • If Ruff finds a ruff.toml file without a target-version, it will check for a pyproject.toml file in the same directory and respect its requires-python version, even if it does not contain a [tool.ruff] section.
  • If Ruff finds a user-level configuration, the requires-python field of the closest pyproject.toml in a parent directory will take precedence.
  • If there is no config file (ruff.tomlor pyproject.toml with a [tool.ruff] section) in the directory of the file being checked, Ruff will search for the closest pyproject.toml in the parent directories and use its requires-python setting.

Stabilization

The following behaviors have been stabilized:

• blanket-noqa (PGH004): Also detect blanked file-level noqa comments (and not just line level comments).

Preview features

• [syntax-errors] Tuple unpacking in for statement iterator clause before Python 3.9 (#16558)

Install ruff 0.11.0

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/ruff/releases/download/0.11.0/ruff-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy ByPass -c "irm https://github.com/astral-sh/ruff/releases/download/0.11.0/ruff-installer.ps1 | iex"
</tr></table> 

... (truncated)

Changelog

Sourced from ruff's changelog.

0.11.0

This is a follow-up to release 0.10.0. Because of a mistake in the release process, the requires-python inference changes were not included in that release. Ruff 0.11.0 now includes this change as well as the stabilization of the preview behavior for PGH004.

Breaking changes

• Changes to how the Python version is inferred when a target-version is not specified (#16319)

  In previous versions of Ruff, you could specify your Python version with:

  • The target-version option in a ruff.toml file or the [tool.ruff] section of a pyproject.toml file.
  • The project.requires-python field in a pyproject.toml file with a [tool.ruff] section.

  These options worked well in most cases, and are still recommended for fine control of the Python version. However, because of the way Ruff discovers config files, pyproject.toml files without a [tool.ruff] section would be ignored, including the requires-python setting. Ruff would then use the default Python version (3.9 as of this writing) instead, which is surprising when you've attempted to request another version.

  In v0.10, config discovery has been updated to address this issue:

  • If Ruff finds a ruff.toml file without a target-version, it will check for a pyproject.toml file in the same directory and respect its requires-python version, even if it does not contain a [tool.ruff] section.
  • If Ruff finds a user-level configuration, the requires-python field of the closest pyproject.toml in a parent directory will take precedence.
  • If there is no config file (ruff.tomlor pyproject.toml with a [tool.ruff] section) in the directory of the file being checked, Ruff will search for the closest pyproject.toml in the parent directories and use its requires-python setting.

Stabilization

The following behaviors have been stabilized:

• blanket-noqa (PGH004): Also detect blanked file-level noqa comments (and not just line level comments).

Preview features

• [syntax-errors] Tuple unpacking in for statement iterator clause before Python 3.9 (#16558)

0.10.0

Check out the blog post for a migration guide and overview of the changes!

Breaking changes

See also, the "Remapped rules" section which may result in disabled rules.

• Changes to how the Python version is inferred when a target-version is not specified (#16319)

  Because of a mistake in the release process, the requires-python inference changes are not included in this release and instead shipped as part of 0.11.0. You can find a description of this change in the 0.11.0 section.

... (truncated)

Commits

• 2cd25ef Ruff 0.11.0 (#16723)
• a22d206 [red-knot] Preliminary tests for typing.Final (#15917)
• 270318c [red-knot] fix: improve type inference for binary ops on tuples (#16725)
• d03b12e [red-knot] Assignments to attributes (#16705)
• 14c5ed5 [pygrep-hooks]: Detect file-level suppressions comments without rul… (#16720)
• 5955650 Fallback to requires-python in certain cases when target-version is not found...
• 2382fe1 [syntax-errors] Tuple unpacking in for statement iterator clause before Pyt...
• 27e9d1f Ruff v0.10 Release (#16708)
• acf35c5 Add new noqa specification to the docs (#16703)
• b9b2562 describe requires-python fallback in docs (#16704)
• 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

[github-actions]

The minor update of this development dependency was automatically approved.