chore(deps): bump the dependencies group across 1 directory with 3 updates by dependabot[bot] · Pull Request #17 · fgcz/fgcz_python_project_template

dependabot · 2026-10-31T07:13:31Z

Bumps the dependencies group with 3 updates in the /.ci/check-tests-structure directory: cyclopts, pytest and pytest-mock.

Updates cyclopts from 5.2.0 to 5.3.2

Release notes

Sourced from cyclopts's releases.

v5.3.2

Bug Fixes

Fix enum members in a Literal (including Parameter(choices=Literal[...])) being shown as Color.RED in help, completion and errors instead of the name that parses (red) by @youdie006 in BrianPugh/cyclopts#1033

New Contributors

@youdie006 made their first contribution in BrianPugh/cyclopts#1033

Full Changelog: BrianPugh/cyclopts@v5.3.1...v5.3.2

v5.3.1

Bug Fixes

respect explicit delimiters for path environment values by @Don-Yin in BrianPugh/cyclopts#1021

validate Parameter(name="*") behind a type alias at setup time by @Rahul-cs50 in BrianPugh/cyclopts#1030

resolve subscripted generic type aliases (#1028) by @yash-bitla in BrianPugh/cyclopts#1031

bind config values to a meta app's own parameters (regressed in v4.0.0) by @BrianPugh in BrianPugh/cyclopts#1027

New Contributors

@Don-Yin made their first contribution in BrianPugh/cyclopts#1021

@Rahul-cs50 made their first contribution in BrianPugh/cyclopts#1030

@yash-bitla made their first contribution in BrianPugh/cyclopts#1031

Full Changelog: BrianPugh/cyclopts@v5.3.0...v5.3.1

v5.3.0

Features

Number validator supports Decimal and Fraction. #988

Bug Fixes

Config & Environment Variables

Empty config containers now bind for dict, list, tuple, set and dataclass parameters (Any parameters keep the container as-is). #993, #1006

A config null is rejected for types that don't allow None. #1004

A config array is rejected for single-value types, including a pydantic Model | bool (previously bound True). #1005, #1014

A JSON config.Env value containing spaces stays one token. #997

Symlinked configuration filenames are preserved. @ac1982 #995

JSON Parsing

dict[str, X] parameters accept a JSON object from the CLI or an env var. #1001

A JSON object for a nested pydantic model field no longer crashes with IndexError. #999

An explicit empty JSON object reports the missing required fields. #992

Errors from config/env JSON list elements name the real parameter instead of --json. #998

Unions With a Class Member

Foo | bool supports keyed fields and bare flags, and lists --x/--no-x in help and shell completion. #991, #1013

Foo | dict[str, int] no longer silently drops unknown keys; its dict fallback keeps typed keys and input order. #1015, #1019

Other

~3.5 ms faster startup and per-invocation overhead. #989

A mistyped command given with --help raises UnknownCommandError. @BreytMN #994

Parameter metadata is honored on dict value types. @saadkhantareen #1008

... (truncated)

Commits

146828c Merge pull request #1033 from youdie006/literal-enum-member-choices
3f57429 fix: don't crash on a nameless Flag value in a Literal
243513d List enum members in a Literal by their transformed name
5c217f9 Merge pull request #1027 from BrianPugh/fix/meta-app-config-params
eea85d9 Merge pull request #1031 from yash-bitla/fix-generic-type-alias-1028
3357a6b fix: resolve generic type alias whose value ignores its type parameter
f98cbb2 fix: validate Parameter(name="*") behind a type alias at setup time
79bcb1d fix: resolve subscripted generic type aliases (#1028)
3b873e9 docs: trim meta-app config docs and docstring
5675265 docs: note that config binds meta app parameters
Additional commits viewable in compare view

Updates 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

Updates pytest-mock from 3.16.0 to 3.17.0

Release notes

Sourced from pytest-mock's releases.

v3.17.0

2026-10-17

#641: Failures of mock assertions such as assert_called_with are again reported only once, instead of two or three times with the original error from the mock module chained before them.

#642: Mock assertion failures no longer show misleading introspection when they are not about the arguments of the last call: assert_called, assert_called_once, assert_not_called, assert_any_call, their await counterparts, and assert_called_once_with/assert_awaited_once_with when the mock was not called (awaited) exactly once. The introspection also no longer reports arguments passed by position versus by keyword as different for autospecced mocks, and no longer shows empty Args:/Kwargs: sections when assertion rewriting is not available.

#643: assert_has_calls and assert_has_awaits failures no longer show pytest introspection, which compared the expected and actual calls position by position and so reported differences between unrelated calls. The mock's own message, listing the expected and actual calls, is still shown.

v3.16.1

2026-10-17

#617: Fixed assert_has_calls raising ValueError instead of AssertionError (or showing misleading introspection) when the expected calls are plain tuples rather than call(...) objects, such as (args, kwargs) entries of another mock's call_args_list, (args,), (kwargs,), (name, args) or (name, kwargs).

#621: Fixed mocker.stop() sometimes stopping the wrong mock, for example with mocks from mocker.create_autospec.

#621: mocker.stop() now undoes the most recent patch first when the same object is used in several patches.

#623: Fixed misleading introspection in assert_has_awaits failures, and assert_has_calls/assert_has_awaits raising IndexError instead of AssertionError when calls is passed by keyword.

#624: Clear spy_return_iter after a spied synchronous or asynchronous function raises, matching spy_return.

#627: Document async_stub await assertions and the distinction between call and await tracking.

#629: Fixed mocker.resetall() skipping the mocks patched with mocker.patch.multiple(), both the ones it creates and the ones passed explicitly.

#630: mocker.resetall() now also resets spy_return and spy_exception of spies, like it already did for spy_return_list and spy_return_iter, and no longer overwrites attributes with these names on mocks that are not spies.

#633: Fixed spies on classmethod, staticmethod, builtins and classes returning a MagicMock instead of calling the spied code after mocker.resetall(side_effect=True). Resetting a spy's side_effect now goes back to calling the spied code, also clearing any side_effect set on the spy.

Changelog

Sourced from pytest-mock's changelog.

3.17.0

2026-10-17

[#641](https://github.com/pytest-dev/pytest-mock/issues/641) <https://github.com/pytest-dev/pytest-mock/pull/641>_: Failures of mock assertions such as assert_called_with are again reported only once, instead of two or three times with the original error from the mock module chained before them.

[#642](https://github.com/pytest-dev/pytest-mock/issues/642) <https://github.com/pytest-dev/pytest-mock/pull/642>_: Mock assertion failures no longer show misleading introspection when they are not about the arguments of the last call: assert_called, assert_called_once, assert_not_called, assert_any_call, their await counterparts, and assert_called_once_with/assert_awaited_once_with when the mock was not called (awaited) exactly once. The introspection also no longer reports arguments passed by position versus by keyword as different for autospecced mocks, and no longer shows empty Args:/Kwargs: sections when assertion rewriting is not available.

[#643](https://github.com/pytest-dev/pytest-mock/issues/643) <https://github.com/pytest-dev/pytest-mock/pull/643>_: assert_has_calls and assert_has_awaits failures no longer show pytest introspection, which compared the expected and actual calls position by position and so reported differences between unrelated calls. The mock's own message, listing the expected and actual calls, is still shown.

3.16.1

2026-10-17

[#617](https://github.com/pytest-dev/pytest-mock/issues/617) <https://github.com/pytest-dev/pytest-mock/pull/617>_: Fixed assert_has_calls raising ValueError instead of AssertionError (or showing misleading introspection) when the expected calls are plain tuples rather than call(...) objects, such as (args, kwargs) entries of another mock's call_args_list, (args,), (kwargs,), (name, args) or (name, kwargs).

[#621](https://github.com/pytest-dev/pytest-mock/issues/621) <https://github.com/pytest-dev/pytest-mock/pull/621>_: Fixed mocker.stop() sometimes stopping the wrong mock, for example with mocks from mocker.create_autospec.

[#621](https://github.com/pytest-dev/pytest-mock/issues/621) <https://github.com/pytest-dev/pytest-mock/pull/621>_: mocker.stop() now undoes the most recent patch first when the same object is used in several patches.

[#623](https://github.com/pytest-dev/pytest-mock/issues/623) <https://github.com/pytest-dev/pytest-mock/pull/623>_: Fixed misleading introspection in assert_has_awaits failures, and assert_has_calls/assert_has_awaits raising IndexError instead of AssertionError when calls is passed by keyword.

[#624](https://github.com/pytest-dev/pytest-mock/issues/624) <https://github.com/pytest-dev/pytest-mock/pull/624>_: Clear spy_return_iter after a spied synchronous or asynchronous function raises, matching spy_return.

[#627](https://github.com/pytest-dev/pytest-mock/issues/627) <https://github.com/pytest-dev/pytest-mock/pull/627>_: Document async_stub await assertions and the distinction between call and await tracking.

[#629](https://github.com/pytest-dev/pytest-mock/issues/629) <https://github.com/pytest-dev/pytest-mock/pull/629>_: Fixed mocker.resetall() skipping the mocks patched with mocker.patch.multiple(), both the ones it creates and the ones passed explicitly.

[#630](https://github.com/pytest-dev/pytest-mock/issues/630) <https://github.com/pytest-dev/pytest-mock/pull/630>_: mocker.resetall() now also resets spy_return and spy_exception of spies, like it already did for spy_return_list and spy_return_iter, and no longer overwrites attributes with these names on mocks that are not spies.

[#633](https://github.com/pytest-dev/pytest-mock/issues/633) <https://github.com/pytest-dev/pytest-mock/pull/633>_: Fixed spies on classmethod, staticmethod, builtins and classes returning a MagicMock instead of calling the spied code after mocker.resetall(side_effect=True). Resetting a spy's side_effect now goes back to calling the spied code, also clearing any side_effect set on the spy.

Commits

5c2f207 Release 3.17.0
9625271 Bump the minor version for releases that change existing behavior
34b87ae Drop introspection from assert_has_calls and assert_has_awaits (#643)
866520f Only show introspection for failures about the call arguments (#642)
5ab41c1 Do not chain the original mock error to wrapped assertion failures (#641)
1916b14 Merge pull request #635 from nicoddemus/docs-contributing-resetall
212fcd9 Document resetall, the changelog format and running tests with tox
9374b2c Merge pull request #634 from pytest-dev/release-3.16.1
fab730d Release 3.16.1
d26d41b Merge pull request #627 from xiehuanyi/docs/async-stub-awaits-20261012-r2
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

…dates Bumps the dependencies group with 3 updates in the /.ci/check-tests-structure directory: [cyclopts](https://github.com/BrianPugh/cyclopts), [pytest](https://github.com/pytest-dev/pytest) and [pytest-mock](https://github.com/pytest-dev/pytest-mock). Updates `cyclopts` from 5.2.0 to 5.3.2 - [Release notes](https://github.com/BrianPugh/cyclopts/releases) - [Commits](BrianPugh/cyclopts@v5.2.0...v5.3.2) Updates `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) Updates `pytest-mock` from 3.16.0 to 3.17.0 - [Release notes](https://github.com/pytest-dev/pytest-mock/releases) - [Changelog](https://github.com/pytest-dev/pytest-mock/blob/main/CHANGELOG.rst) - [Commits](pytest-dev/pytest-mock@v3.16.0...v3.17.0) --- updated-dependencies: - dependency-name: cyclopts dependency-version: 5.3.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dependencies - dependency-name: pytest dependency-version: 9.2.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: dependencies - dependency-name: pytest-mock dependency-version: 3.17.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: dependencies ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot Bot added dependencies Pull requests that update a dependency file python:uv Pull requests that update python:uv code labels Oct 31, 2026

Navigation Menu

Repository navigation

chore(deps): bump the dependencies group across 1 directory with 3 updates - #17

chore(deps): bump the dependencies group across 1 directory with 3 updates#17
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/dot-ci/check-tests-structure/dependencies-ac7120b26b

dependabot Bot commented on behalf of github Oct 31, 2026

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

dependabot Bot commented on behalf of github Oct 31, 2026

v5.3.2

Bug Fixes

New Contributors

v5.3.1

Bug Fixes

New Contributors

v5.3.0

Features

Bug Fixes

Config & Environment Variables

JSON Parsing

Unions With a Class Member

Other

9.2.0

pytest 9.2.0 (2026-10-27)

Removals and backward incompatible breaking changes

Deprecations (removal in next major release)

New features

Improvements in existing functionality

v3.17.0

v3.16.1

3.17.0

3.16.1

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants