Skip to content

Bump pytest from 9.1.1 to 9.2.0 - #190

Merged
docktermj merged 1 commit into
mainfrom
dependabot/pip/pytest-9.2.0
Nov 18, 2026
Merged

docktermj merged 1 commit into
mainfrom
dependabot/pip/pytest-9.2.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Bumps pytest from 9.1.1 to 9.2.0.

Release notes

Sourced from pytest's releases.

9.2.0

pytest 9.2.0 (2026-10-27)

Removals and backward incompatible breaking changes

  • #14716: -c now raises a usage error for a path that does not exist, is a directory, or is in a format pytest has no loader for. Such paths were previously either ignored or reported as an unhandled FileNotFoundError.

  • #8593: The indirect, ids and scope arguments of Metafunc.parametrize() <pytest.Metafunc.parametrize> -- and therefore of @pytest.mark.parametrize <pytest.mark.parametrize ref> -- are now keyword-only.

    Passing them positionally was a common source of confusing errors, e.g. parametrize("arg1", "arg2", [(1, 2)]) made the argvalues land in indirect and failed with indirect fixture '(1, 2)' doesn't exist; such mistakes now fail with an understandable TypeError. The type annotations have always declared these arguments as keyword-only.

  • #993: Plugin import failures at startup are now reported and classified instead of escaping as a raw traceback with the accidental exit code 1:

    • a plugin that cannot be found -- via -p, pytest_plugins or PYTEST_PLUGINS -- exits with pytest.ExitCode USAGE_ERROR (4), like a conftest.py that fails to import;
    • a plugin that is found but raises while importing -- including a broken pytest11 entry point or a missing plugin dependency -- exits with pytest.ExitCode INTERNAL_ERROR (3), with the traceback preserved.

    pytest.main now returns these codes instead of raising ImportError. Also fixed an IndexError from pytest's own internals when the plugin raised an exception with no arguments.

Deprecations (removal in next major release)

  • #14742: The private _pytest.python.CallSpec2 name has been renamed to CallSpec. The old CallSpec2 alias remains available for now and will be removed in pytest 10 or 11.

  • #14755: Schedule yield_fixture decorator for removal in pytest 10 or 11.

  • #14774: Similarly to the deprecation of class-scoped fixtures defined as instance methods in pytest 9.1, all higher-scoped fixtures (module, package, and session) defined as instance methods are now deprecated.

    They suffer from the same issue the original deprecation only fixed for class-scoped fixtures, see 10819 and 14011.

  • #14808: Passing a non-string value to a string-typed ini option now emits a pytest.PytestRemovedIn10Warning. This affects [tool.pytest.ini_options] in pyproject.toml. In pytest 10 this will raise a TypeError, matching the behavior of the corresponding TOML config path.

  • #7323: Passing bytes to TerminalReporter.write_line() is now deprecated, pass a str instead.

New features

  • #14743: Full diff: now contains a legend explaining the + & - symbols in diff output.
  • #2781: When strict_markers is enabled, marker names used in -m expressions are now validated against registered markers.
  • #6881: Added the parametrize_long_str_id_strategy configuration option to control how long str/bytes parameter values are handled in auto-generated test IDs. Explicit IDs set via ids=[...] or pytest.param(..., id=...) are not affected. Available strategies: short (default, values over 100 chars fall back to argname+index), sha256 (SHA-256 hex digest), legacy (keep full value), and disallow (error requesting explicit IDs).

Improvements in existing functionality

  • #10745: A RecursionError whose recursion origin cannot be located now shows only the first and last 10 stack frames, matching what pytest already did when locating the origin failed outright. Previously the full traceback -- often around a thousand near-identical frames -- was rendered, which was both slow and unreadable. Pass --full-trace to see every frame.

... (truncated)

Commits
  • ae1d0ff Prepare release version 9.2.0
  • 143ce31 pre-commit: exclude codespell on generated release announcements
  • 532dc5f tox: add attrs dependency to regen, needed in reportingdemo.rst
  • a7b2446 Merge pull request #15245 from pytest-dev/claude/project-thread-9jcf91
  • 679d09c [pre-commit.ci] pre-commit autoupdate (#15266)
  • 41d12cd docs: clarify typing for yield fixtures
  • b9022ba Merge pull request #15182 from 1871698/docs/improve-getting-started-description
  • 16f87a7 docs: improve getting-started.rst test execution description
  • 082ed70 Merge pull request #15255 from pytest-dev/claude/project-thread-eoi3d6
  • ae37a01 Merge pull request #15227 from pytest-dev/claude/project-thread-4etye4
  • Additional commits viewable in compare view

@dependabot
dependabot Bot requested a review from a team as a code owner November 18, 2026 01:32
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Nov 18, 2026
@github-actions

Copy link
Copy Markdown

🤖 Claude Code Review

PR Review: Bump pytest 9.1.1 → 9.2.0

The diff changes pyproject.toml only. It bumps pytest for python_version > '3.11' in two places: the development group (line 44) and the test group (line 85).

Code Quality

  • ✅ Style: The change keeps the existing pinned-version format and the Python-version markers.
  • ✅ No commented-out code.
  • ✅ Naming and DRY: Not applicable. The pin appears in two dependency groups, which is the repo's existing layout, and both are updated consistently.
  • ✅ Defects: None found. The python_version <= '3.11' pin (pytest==8.4.2) is untouched, which is correct. pytest 9.x requires a newer Python, which is why the pins are split. I did not verify that 9.2.0 supports every Python version in the > 3.11 range, so CI should confirm it.
  • ✅ .claude/CLAUDE.md: It is unchanged and contains nothing specific to a local environment.

Testing

  • ✅ New functions and endpoints: None are added, so no new tests are needed.
  • ⚠️ Coverage: No coverage change is expected. Confirm that CI passes under pytest 9.2.0, including pytest-cov==7.1.0 and pytest-schema==0.1.2, which are not bumped in this PR.

Documentation

  • ✅ README and API docs: No updates needed.
  • ⚠️ CHANGELOG.md: The diff does not touch it. Dependabot bumps are usually not logged, but if this project records dependency updates, add an entry.
  • ✅ Markdown: No Markdown files changed.

Security

  • ✅ Credentials, input validation, error handling, logs: Not affected.
  • ✅ License files: No .lic files or AQAAAD strings are in the diff.

Summary

This is a low-risk, routine dev and test dependency bump. I have no blocking issues. Merge once CI is green. Optionally add a CHANGELOG entry if the project tracks dependency updates.

Automated code review analyzing defects and coding standards

Bumps [pytest](https://github.com/pytest-dev/pytest) from 9.1.1 to 9.2.0.
- [Release notes](https://github.com/pytest-dev/pytest/releases)
- [Changelog](https://github.com/pytest-dev/pytest/blob/main/CHANGELOG.rst)
- [Commits](pytest-dev/pytest@9.1.1...9.2.0)

---
updated-dependencies:
- dependency-name: pytest
  dependency-version: 9.2.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/pip/pytest-9.2.0 branch from 17893ae to f4f595b Compare November 18, 2026 14:03
@github-actions

Copy link
Copy Markdown

🤖 Claude Code Review

PR Code Review: Bump pytest 9.1.1 → 9.2.0

The diff changes pyproject.toml only. It bumps pytest for python_version > '3.11' in two places: the development group (line 44) and the test group (line 85).

Code Quality

  • ✅ Style: The pins use the same format as the surrounding entries.
  • ✅ No commented-out code.
  • ✅ Naming and DRY: Not applicable. The pin appears in both development and test, but this is the existing layout and both occurrences were updated together.
  • ✅ Defects: I found none. The python_version <= '3.11' pin stays at 8.4.2, as before. I did not check whether 9.2.0 is compatible with pytest-cov==7.1.0, pytest-schema==0.1.2 or coverage==7.16.2, so CI should confirm that.
  • ✅ .claude/CLAUDE.md: It is unchanged by this PR. It contains nothing specific to a local environment.

Testing

  • ✅ New functions and endpoints: There is no new code, so no new tests are needed.
  • ⚠️ Coverage: I did not measure it. CI will exercise the new pytest version, and that run is the check on this bump.

Documentation

  • ⚠️ CHANGELOG.md: It is not updated. Dependabot bumps of dev and test dependencies usually don't need an entry, so this is optional. Follow the project's convention if it logs them.
  • ✅ README and API docs: No changes are needed.
  • ✅ Markdown: No Markdown files changed.

Security

  • ✅ No hardcoded credentials, license files or AQAAAD strings.
  • ✅ Input validation, error handling and logging: Not applicable.
  • ✅ Supply chain: The version is pinned exactly, and it is a dev/test-only dependency. It does not ship in the runtime package.

Summary

This is a low-risk, mechanical dev-dependency bump with no blocking issues. I recommend approval once CI passes.

Automated code review analyzing defects and coding standards

@docktermj
docktermj merged commit e0f801a into main Nov 18, 2026
12 checks passed
@docktermj
docktermj deleted the dependabot/pip/pytest-9.2.0 branch November 18, 2026 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file python Pull requests that update python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant