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

dependabot · 2026-11-07T07:13:45Z

Bumps the dependencies group with 5 updates in the /.ci/check-tests-structure directory:

Package	From	To
cyclopts	`5.2.0`	`5.3.3`
pydantic	`2.14.1`	`2.14.2`
pyfakefs	`6.2.0`	`6.3.2`
pytest	`9.1.1`	`9.2.0`
pytest-mock	`3.16.0`	`3.17.0`

Updates cyclopts from 5.2.0 to 5.3.3

Release notes

Sourced from cyclopts's releases.

v5.3.3

Bug Fixes

convert NewType nested inside containers and unions to its underlying type by @Enesuygurs in BrianPugh/cyclopts#1036

show choices for an enum NewType nested in a container or union by @BrianPugh in BrianPugh/cyclopts#1038

complete default-command positionals alongside subcommands in bash/zsh/fish by @BrianPugh in BrianPugh/cyclopts#1037

New Contributors

@Enesuygurs made their first contribution in BrianPugh/cyclopts#1036

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

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

... (truncated)

Commits

e512a49 fix: complete default-command positionals alongside subcommands in bash/zsh/fish
7919e99 fix: list choices for an enum NewType nested in a container or union
11004d5 fix: convert NewType nested inside containers and unions to its underlying type
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
Additional commits viewable in compare view

Updates pydantic from 2.14.1 to 2.14.2

Release notes

Sourced from pydantic's releases.

v2.14.2 2026-10-29

v2.14.2 (2026-10-29)

This release addresses 2 security issues, GHSA-qpmf-fgh3-ff25 and GHSA-3r8g-cqwr-jr29.

Packaging

Bump PyO3 to 0.30.1, jiter to 0.18.0, use PyFrozenDict by @Viicos in #14003

Bump speedate to v0.18.0 by @Viicos in #14007

Publish pydantic-core wheels for PyPy 8.0 (pp80 ABI) by @Viicos in #14083

Performance

Avoid Python tuple allocation during model fields validation by @Viicos in #13955

Lazily call repr of values during nested union serialization by @Viicos in #14082

Skip decorator field checks when no field decorators exist by @alexmojaki in #14111

Avoid heap allocation for small JSON model field buffers by @alexmojaki in #14113

Fixes
Make JSON validation by iteration consistent with Python approach by @davidhewitt in #13275.

JSON validation now handles field lookup and extra data the same way as Python validation. In particular, keys that only match an unused alias or field name are now treated as extra data, instead of being silently dropped:
from pydantic import BaseModel, ConfigDict
from pydantic.alias_generators import to_camel
class Page(BaseModel):
model_config = ConfigDict(extra='forbid', alias_generator=to_camel)
page_size: int = 10

Page.model_validate_json('{"page_size": 50}')
Before: Page(page_size=10)
After: ValidationError (extra_forbidden)
See the pull request for the full list of behavior changes. This change addresses GHSA-qpmf-fgh3-ff25.
Ignore extra data matching a field name in TypedDict and dataclasses with extra=allow by @Viicos in #14090. Addresses GHSA-3r8g-cqwr-jr29.

Fix unpickling of generic classes defined in separate module by @Viicos in #13994

Support explicit by_alias overriding validate_by_alias in validation JSON schemas by @Viicos in #13997

Fix mypy plugin crash on deferred empty model by @ilevkivskyi in #14027

Fix infinite recursion when validating an invalid default with PydanticUseDefault by @Viicos in #14028

Implement recursion guard for validate_strings() by @Viicos in #14029

... (truncated)

Changelog

Sourced from pydantic's changelog.

v2.14.2 (2026-10-29)

GitHub release

What's Changed

Packaging

Bump PyO3 to 0.30.1, jiter to 0.18.0, use PyFrozenDict by @Viicos in #14003

Bump speedate to v0.18.0 by @Viicos in #14007

Publish pydantic-core wheels for PyPy 8.0 (pp80 ABI) by @Viicos in #14083

Performance

Avoid Python tuple allocation during model fields validation by @Viicos in #13955

Lazily call repr of values during nested union serialization by @Viicos in #14082

Skip decorator field checks when no field decorators exist by @alexmojaki in #14111

Avoid heap allocation for small JSON model field buffers by @alexmojaki in #14113

Fixes
Make JSON validation by iteration consistent with Python approach by @davidhewitt in #13275.

JSON validation now handles field lookup and extra data the same way as Python validation. In particular, keys that only match an unused alias or field name are now treated as extra data, instead of being silently dropped:
from pydantic import BaseModel, ConfigDict
from pydantic.alias_generators import to_camel
class Page(BaseModel):
model_config = ConfigDict(extra='forbid', alias_generator=to_camel)
page_size: int = 10

Page.model_validate_json('{"page_size": 50}')
Before: Page(page_size=10)
After: ValidationError (extra_forbidden)
See the pull request for the full list of behavior changes.
Fix unpickling of generic classes defined in separate module by @Viicos in #13994

Support explicit by_alias overriding validate_by_alias in validation JSON schemas by @Viicos in #13997

Fix mypy plugin crash on deferred empty model by @ilevkivskyi in #14027

Fix infinite recursion when validating an invalid default with PydanticUseDefault by @Viicos in #14028

Implement recursion guard for validate_strings() by @Viicos in #14029

Support named tuples in Sequence serialization by @Viicos in #14033

... (truncated)

Commits

aa540ac Update changelog for v2.14.2
6cde12f Update changelog for v2.14.2
2db7c25 Fix deep copy of self-referential models
d783154 Update changelog for v2.14.2
df49b6c Avoid heap allocation for small JSON model field buffers
cd93e69 Skip decorator field checks when no field decorators exist
2771e57 Make JSON validation by iteration consistent with Python approach
8102e3f Avoid Python tuple allocation during model fields validation
dd139b5 Bump pydantic.v1 namespace to v1.10.27
66155f9 Prepare release v2.14.2
Additional commits viewable in compare view

Updates pyfakefs from 6.2.0 to 6.3.2

Release notes

Sourced from pyfakefs's releases.

pyfakefs release version 6.3.2

really fixes the regression causing exceptions with django present (version 6.3.1 did not)

pyfakefs release version 6.3.1

fixes a regression causing exceptions with django present

pyfakefs release version 6.3.0

adds official Python 3.15 support

see the release notes for a list of changes

Changelog

Sourced from pyfakefs's changelog.

Version 6.3.2 (2026-11-03)

Fixes a regression in the latest release causing an exception if django was available.

Fixes

regression: removed cleanup of django view modules, which has not been working for some time and now caused an exception (which was caught in the previous versions), see #1367

Version 6.3.0 (2026-11-01)

Adds official Python 3.15 support.

Changes

some minor macOS-specific behavior changes to match the behavior of the current macOS version used in CI (see #1327)

changed handling of path separators for cross-platform tests to be more consistent with the simulated OS; this may break some existing tests that assume the old behavior

added official support for Python 3.15

Fixes

fixed Path.glob() not finding literal pattern parts with a different case in a case-insensitive filesystem (e.g. macOS) under Python 3.14 (see #1347)

fixed resolving Windows drive-relative paths (see #1324)

fixed os.path.sameopenfile using real file descriptors instead of fake ones (see #1346)

fixed a crash if the stack limit was set to a low value (see #1313)

fixed os.ftruncate to inspect the FakeFileWrapper returned by get_open_file(fd) (see #1331)

fixed cross-device hard links incorrectly succeeding (see #1337)

fixed os.rename failing for the root user in a directory owned by another user (see #1341)

fixed os.path.basename, os.path.splitext and os.path.commonpath not using the path semantics of the simulated file system (see #1348)

fixed handling of unhashable types

fixed shutil.rmtree() failing on directories containing symlinks to directories with Python >= 3.12.4 by supporting os._walk_symlinks_as_files in os.walk() (see #1363)

Infrastructure

report CPU time for warmed-up cached and uncached setup/cleanup cycles in the

... (truncated)

Commits

c3aa992 Release 6.3.2
98931ac Pin Fedora docker image to 44
7dea328 Remove cleanup of django packages
e955a6a Release 6.3.1
7900bbe Release 6.3.0
f43fce4 Add official support for Python 3.15
bf505be [pre-commit.ci] pre-commit autoupdate
9ba83fd Fix shutil.rmtree on directories containing symlinks to directories (#1364)
ead6056 [pre-commit.ci] pre-commit autoupdate
a4285b9 More handling of unhashable types
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 5 updates in the /.ci/check-tests-structure directory: | Package | From | To | | --- | --- | --- | | [cyclopts](https://github.com/BrianPugh/cyclopts) | `5.2.0` | `5.3.3` | | [pydantic](https://github.com/pydantic/pydantic) | `2.14.1` | `2.14.2` | | [pyfakefs](https://github.com/pytest-dev/pyfakefs) | `6.2.0` | `6.3.2` | | [pytest](https://github.com/pytest-dev/pytest) | `9.1.1` | `9.2.0` | | [pytest-mock](https://github.com/pytest-dev/pytest-mock) | `3.16.0` | `3.17.0` | Updates `cyclopts` from 5.2.0 to 5.3.3 - [Release notes](https://github.com/BrianPugh/cyclopts/releases) - [Commits](BrianPugh/cyclopts@v5.2.0...v5.3.3) Updates `pydantic` from 2.14.1 to 2.14.2 - [Release notes](https://github.com/pydantic/pydantic/releases) - [Changelog](https://github.com/pydantic/pydantic/blob/v2.14.2/HISTORY.md) - [Commits](pydantic/pydantic@v2.14.1...v2.14.2) Updates `pyfakefs` from 6.2.0 to 6.3.2 - [Release notes](https://github.com/pytest-dev/pyfakefs/releases) - [Changelog](https://github.com/pytest-dev/pyfakefs/blob/main/CHANGES.md) - [Commits](pytest-dev/pyfakefs@v6.2.0...v6.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.3 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dependencies - dependency-name: pydantic dependency-version: 2.14.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dependencies - dependency-name: pyfakefs dependency-version: 6.3.2 dependency-type: direct:development 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 Nov 7, 2026

Navigation Menu

Repository navigation

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

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

dependabot Bot commented on behalf of github Nov 7, 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 Nov 7, 2026

v5.3.3

Bug Fixes

New Contributors

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

v2.14.2 2026-10-29

v2.14.2 (2026-10-29)

Packaging

Performance

Fixes

v2.14.2 (2026-10-29)

What's Changed

Packaging

Performance

Fixes

pyfakefs release version 6.3.2

pyfakefs release version 6.3.1

pyfakefs release version 6.3.0

Version 6.3.2 (2026-11-03)

Fixes

Version 6.3.0 (2026-11-01)

Changes

Fixes

Infrastructure

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