Repository navigation
Update dependency pydantic-settings to v2.16.3 - #21
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==2.16.2→==2.16.3Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
pydantic/pydantic-settings (pydantic-settings)
v2.16.3Compare 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.serializeround-trip bug withCliUnknownArgs.Security
SecretsSettingsSourceno longer follows symlinks that resolve outsidesecrets_dir(#1138, fixes #1137). A secret file that is a symbolic link to a file outsidesecrets_dirwas read into the matching field, so anyone who could place a link insecrets_dircould 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 onlyNestedSecretsSettingsSource. Links that stay insidesecrets_dir, such as the Kubernetes secret volume layout (passwdlinking to..data/passwd), still work.Behavior changes
secrets_diris 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 intosecrets_dir, or pointsecrets_dirat the directory that holds them.NestedSecretsSettingsSourceskips hidden entries (names starting with.) again, as it did before 2.14.2, and stops with aSettingsErrorafter 10,000 entries (#1070).Bug fixes
Secrets
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 (dblinking to..data/db) silently lost its nested secrets.secrets_diris skipped instead of aborting the load withRuntimeErroron Python 3.11 and 3.12 (#1070, #1138).CLI
CliApp.serializekeeps each level'sCliUnknownArgsbefore 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
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.