Skip to content

fix(deps): update dependency pydantic-settings to >=2.16.3,<2.17.0 - #369

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/pydantic-settings-2.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/pydantic-settings-2.x

Conversation

@renovate

@renovate renovate Bot commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
pydantic-settings (changelog) >=2.15.0,<2.16.0 → >=2.16.3,<2.17.0 age confidence

Release Notes

pydantic/pydantic-settings (pydantic-settings)

v2.16.3

Compare Source

Highlights

This patch release fixes a security issue in the default secrets source, a regression from 2.14.2 that dropped nested secrets on Kubernetes, and a CliApp.serialize round-trip bug with CliUnknownArgs.

Security
  • SecretsSettingsSource no longer follows symlinks that resolve outside secrets_dir (#​1138, fixes #​1137). A secret file that is a symbolic link to a file outside secrets_dir was read into the matching field, so anyone who could place a link in secrets_dir could make the application load any file it can read. This is the plain-source counterpart of GHSA-4xgf-cpjx-pc3j, whose fix in 2.14.2 covered only NestedSecretsSettingsSource. Links that stay inside secrets_dir, such as the Kubernetes secret volume layout (passwd linking to ..data/passwd), still work.
Behavior changes
  • A secret file that resolves outside secrets_dir is now skipped with a warning instead of being read (#​1138). If you deliberately point secret files at targets elsewhere on disk, move or copy the targets into secrets_dir, or point secrets_dir at the directory that holds them.
  • NestedSecretsSettingsSource skips hidden entries (names starting with .) again, as it did before 2.14.2, and stops with a SettingsError after 10,000 entries (#​1070).
Bug fixes

Secrets

  • With secrets_nested_subdir=True, a directory reached through a second symlink is loaded again (#​1070, fixes #​1061). Since 2.14.2, only the name that sorted first was walked, so the standard Kubernetes secret volume layout (db linking to ..data/db) silently lost its nested secrets.
  • A symlink loop inside secrets_dir is skipped instead of aborting the load with RuntimeError on Python 3.11 and 3.12 (#​1070, #​1138).

CLI

  • CliApp.serialize keeps each level's CliUnknownArgs before that level's subcommand token (#​1050, fixes #​1048). They were emitted after the last subcommand, so parsing the output again moved a parent's unknown args onto the subcommand.
All changes

What's Changed

New Contributors

Full Changelog: pydantic/pydantic-settings@v2.16.2...v2.16.3

v2.16.2

Compare Source

Highlights

This patch release fixes env decoding of nested dictionary values, CliApp handling of AliasPath, nested secrets directory precedence and discriminated union defaults with nested_model_default_partial_update.

Behavior changes
  • An explicit secrets_dir on NestedSecretsSettingsSource now takes precedence (#​1093). Previously it was ignored when the wrapped SecretsSettingsSource inherited a directory from model config, and an explicit empty list was masked too. The order is now: the wrapper's secrets_dir argument, then the wrapped source's directory, then model config. If you pass both Settings(_secrets_dir=...) and NestedSecretsSettingsSource(..., secrets_dir=...), the wrapper's argument now wins.
Bug fixes

Env and dotenv sources

  • Dictionary values typed as a union, such as dict[str, list[str] | str] or dict[str, list[str] | None], now JSON-decode values set through env_nested_delimiter (#​1089, #​1097). Only JSON arrays and objects are decoded, so plain values like 123, true or "quoted" are kept as strings. Decoding follows enable_decoding and the NoDecode/ForceDecode of the field that holds the dict, and type aliases and Annotated value types are resolved.
  • Nested dictionary values such as dict[str, list[dict[str, str]]] are decoded at the right level again (#​1109), so APP_VALUES__X='[{"k":"v"}]' no longer reaches validation as a string.

CLI

  • CliApp.run now rebuilds AliasPath inputs for BaseModel and pydantic dataclass commands (#​1096). A supplied path used to be reduced to the field name, which failed validation. AliasChoices priority is respected and unsupplied path defaults are left to the model.

Discriminated union defaults

  • With nested_model_default_partial_update=True, inner discriminated unions written as Annotated[..., Field(discriminator='...')] are now detected (#​1076). When the incoming tag selects another member, the default's fields are no longer merged into it.
  • A stdlib dataclass default on a discriminated union field no longer raises NameError when another field of the dataclass has a string annotation naming a local class (#​1077). Only the discriminator's own annotation is resolved now.
All changes (including dependency bumps and internal maintenance)

What's Changed

New Contributors

Full Changelog: pydantic/pydantic-settings@v2.16.1...v2.16.2

v2.16.1

Compare Source

Highlights

This patch release fixes two CLI regressions introduced in 2.16.0.

Bug fixes

CLI

  • Fixed-length tuple positionals such as CliPositionalArg[tuple[int, int]] and NamedTuples are single-valued again (#​1069). Since 2.16.0 they were treated as variadic, so a CLI either refused to start with a SettingsError or put the wrong argument into the tuple. Variable-length tuples (tuple[int, ...] and bare Tuple) are still variadic.
  • A field typed as an alias of a list of dicts, e.g. type ListOfDict = list[dict[str, int]], accepts a JSON list again (#​1049). Since 2.16.0, --xx '[{"a":1},{"b":2}]' was merged into the single dict {"a": 1, "b": 2} and failed validation.
All changes (including dependency bumps and internal maintenance)

What's Changed

Full Changelog: pydantic/pydantic-settings@v2.16.0...v2.16.1

v2.16.0

Compare Source

Highlights

Breaking changes and behavior changes
  • Python 3.10 is no longer supported (#​1003). pydantic-settings now requires Python 3.11+, since 3.10 reaches end of life this month. The tomli fallback is gone in favor of stdlib tomllib; the toml extra is kept as an empty extra so pip install pydantic-settings[toml] keeps working.
  • python-dotenv>=1.2.2 is now required (#​971) to pick up the fix for CVE-2026-28684.
  • Aliases are ignored in every source when validate_by_alias=False (#​1033). Env vars, secrets, CLI flags and defaults now use only field names, matching pydantic. An env var named after the alias is now ignored instead of raising extra_forbidden, and the CLI exposes --apple rather than --pomo.
  • validation_alias takes precedence over alias (#​1038). When the two differ, values from JSON/YAML/TOML files and the CLI were silently ignored; they now load. CLI help lists the validation_alias flag first, and CliApp.serialize emits it.
  • CLI case-insensitivity only lowercases registered options (#​1036). With case_sensitive=False, args after -- and those captured by CliUnknownArgs keep their case (-Xmx4G no longer becomes -xmx4g). Unrecognized options are now reported as typed (--NOPE instead of --nope).
  • JSON and YAML config files are read as UTF-8 by default (#​955) instead of the locale encoding, completing the secrets-file fix from 2.15.0. json_file_encoding/yaml_file_encoding still override it.
  • Discriminated union defaults are partially updated again (#​997). This reverts the 2.15.0 regression with nested_model_default_partial_update=True: the default is only dropped when the incoming value selects a different union member.
New features
  • Python 3.15 and pydantic 2.14 support (#​1026, #​1029, #​1022). pydantic 2.14 broke CliApp.run and validate_by_alias=False handling; both are fixed.
  • Cached settings instances via Settings.settings_cached() and Settings.settings_clear_cache() (#​952). These give you a process-local singleton per settings class without hand-rolling lru_cache wrappers. Calling the class directly still builds a fresh instance.
  • AWS Systems Manager Parameter Store source — AWSSystemsManagerSettingsSource (#​941). It recursively reads every parameter under an ssm_path, with / mapping onto nested models. Install it with the new aws-systems-manager extra.
  • env_file_depth (#​940) lets a relative env_file be found in parent directories, mirroring pyproject_toml_depth. This is useful when scripts run from a subdirectory of a monorepo. It defaults to 0, which keeps the current behavior.
  • CliVariadicArg for named variadic options (#​949, #​958). It accepts --param a b c in addition to repeated --param a --param b. Required fields need at least one value.
Bug fixes

CLI

  • CliApp.serialize output now round-trips through CliApp.run for enums, tuples, dates and Decimals (#​988), explicit None values (#​981), empty containers (#​1008), CliVariadicArg values (#​976) and populated CliUnknownArgs fields, which previously raised IndexError (#​992).
  • Empty JSON arrays (--items []) now give an empty list instead of [''] (#​994).
  • Tuples, frozenset, MutableSequence and other collection subtypes are now treated as repeatable/variadic options (#​972), and so are named collection type aliases such as TypeAliasType('Addrs', list[IPvAnyAddress]) (#​1032).
  • cli_exit_on_error=False is now honored in CliSubCommand parsers, which raise SettingsError instead of exiting (#​977).
  • CliSubCommand aliases keep their case with case_sensitive=False (#​989).
  • Each CliUnknownArgs field now receives only its own subcommand's leftover args (#​1004).
  • CliApp.format_help no longer crashes when cli_prefix is set in model_config (#​945).

Type aliases and parsing

  • Named union type aliases (TypeAliasType('V', list[int] | str)) now decode like their inline equivalents in env and dotenv sources, including under Optional, Annotated and custom validation aliases (#​1006, #​1030, #​1041).
  • Resolving a named Annotated type alias no longer mutates shared FieldInfo metadata, which made validators run twice on subclasses or after model_rebuild() (#​979).
  • A bare single-segment AliasPath('SOME_KEY') no longer tries to JSON-decode plain string values (#​980).
  • collections.abc.Set/MutableSet/typing.AbstractSet fields now JSON-decode env values (#​973).
  • A bare typing.Dict field with env_nested_delimiter no longer raises IndexError, which was a regression in 2.13.0 (#​1009).
  • Case-insensitive matching now works for nested pydantic dataclasses (#​1010).

Dotenv, secrets and config files

  • With extra='allow', a non-lowercase env_prefix is now stripped from dotenv extras (#​959, #​968).
  • secrets_case_sensitive=True is now honored on Windows (#​1001).
  • An empty JSON config file is treated as an empty mapping instead of crashing (#​947), matching YAML and TOML.
  • TOML table headers: ~ paths are now expanded when checking that the file exists (#​1034), and an explicit toml_table_header=() now overrides the model config to read the file root (#​1027).

Cloud sources

  • Azure Key Vault and GCP Secret Manager now honor env_parse_none_str (#​1019, #​1040).
  • Azure Key Vault: dash_to_underscore=True now works for nested model fields (#​1025).
  • NestedSecretsSettingsSource now validates its specific constructor arguments (#​975).
  • DotenvFiltering is exported from pydantic_settings.sources.types (#​944).
Documentation
  • Document that runtime validation arguments (strict, extra, context) passed to model_validate() are not applied to BaseSettings, and give a workaround (#​1017).
  • Explain why extra='forbid' doesn't reject misspelled top-level env vars (#​986).
  • Clarify alias plus nested model env lookup with populate_by_name (#​933), and add a nested model example for env_prefix_target (#​953).
  • Fix assorted typos (#​942, #​964).
All changes (including dependency bumps and internal maintenance)

What's Changed

New Contributors

Full Changelog: pydantic/pydantic-settings@v2.15.0...v2.16.0


Configuration

📅 Schedule: (in timezone Europe/Paris)

  • Branch creation
    • At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday (* 0-4,22-23 * * 1-5)
    • Only on Sunday and Saturday (* * * * 0,6)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copilot AI balanced review requested due to automatic review settings October 22, 2026 20:56
@renovate renovate Bot added dependencies Pull requests that update a dependency file. filigran team Item from the Filigran team. labels Oct 22, 2026

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No blocking compatibility issues were identified with the supported Python baseline or existing settings usage; installation and tests were not run.

No open issues 🎉

What changed in this PR

Updates the Python client’s pydantic-settings dependency to the 2.16 release series.

Changes:

  • Raises the dependency range from >=2.15.0,<2.16.0 to >=2.16.0,<2.17.0.
File Description
pyproject.toml Updates the allowed pydantic-settings version range.

Review effort: Balanced

@renovate
renovate Bot force-pushed the renovate/pydantic-settings-2.x branch from b5dd608 to 2e49402 Compare October 23, 2026 23:16
@renovate renovate Bot changed the title fix(deps): update dependency pydantic-settings to >=2.16.0,<2.17.0 fix(deps): update dependency pydantic-settings to >=2.16.1,<2.17.0 Oct 23, 2026
@renovate
renovate Bot force-pushed the renovate/pydantic-settings-2.x branch 2 times, most recently from 09e5bf9 to 81d1b94 Compare October 31, 2026 12:42
@renovate renovate Bot changed the title fix(deps): update dependency pydantic-settings to >=2.16.1,<2.17.0 fix(deps): update dependency pydantic-settings to >=2.16.2,<2.17.0 Oct 31, 2026
@renovate
renovate Bot force-pushed the renovate/pydantic-settings-2.x branch from 81d1b94 to 2e799aa Compare November 12, 2026 03:26
@renovate
renovate Bot force-pushed the renovate/pydantic-settings-2.x branch from 2e799aa to 92754c6 Compare November 17, 2026 01:35
@renovate renovate Bot changed the title fix(deps): update dependency pydantic-settings to >=2.16.2,<2.17.0 fix(deps): update dependency pydantic-settings to >=2.16.3,<2.17.0 Nov 17, 2026
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. filigran team Item from the Filigran team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant