Bump pydantic-settings from 2.1.0 to 2.2.0

[dependabot]

Bumps pydantic-settings from 2.1.0 to 2.2.0.

Release notes

Sourced from pydantic-settings's releases.

v2.2.0

What's Changed

• Fix documentation and update pydantic and pydantic-core dependancies by @​Xunop in pydantic/pydantic-settings#194
• Correct a typo in README.md by @​felixonmars in pydantic/pydantic-settings#195
• feat: ignore empty env vars by @​niventc in pydantic/pydantic-settings#198
• Allow nested env var source to override nested init source. by @​kschwab in pydantic/pydantic-settings#204
• Fix typo in explode_env_vars() docstring by @​paytonward6 in pydantic/pydantic-settings#207
• Add support for parsing environment "None" strings to None. by @​kschwab in pydantic/pydantic-settings#206
• Ensure extra='forbid' is enforced in DotEnvSettingsSource when env_prefix is specified by @​kjithin in pydantic/pydantic-settings#218
• Fix for JSON on optional nested types. by @​kschwab in pydantic/pydantic-settings#217
• Improve docs by @​hramezani in pydantic/pydantic-settings#225
• feat: adding json, yaml and toml sources by @​Smixi in pydantic/pydantic-settings#211
• Fix dotenv source extra values parsing provided in dotenv file by @​hramezani in pydantic/pydantic-settings#221
• Update requirements by @​hramezani in pydantic/pydantic-settings#233
• Prepare release 2.2.0 by @​hramezani in pydantic/pydantic-settings#232

New Contributors

• @​Xunop made their first contribution in pydantic/pydantic-settings#194
• @​felixonmars made their first contribution in pydantic/pydantic-settings#195
• @​niventc made their first contribution in pydantic/pydantic-settings#198
• @​kschwab made their first contribution in pydantic/pydantic-settings#204
• @​paytonward6 made their first contribution in pydantic/pydantic-settings#207
• @​kjithin made their first contribution in pydantic/pydantic-settings#218
• @​Smixi made their first contribution in pydantic/pydantic-settings#211

Full Changelog: pydantic/pydantic-settings@v2.1.0...v2.2.0

Commits

• 965d1b4 Prepare release 2.2.0 (#232)
• cde78d8 Update requirements (#233)
• 15b66df Fix dotenv source extra values parsing provided in dotenv file (#221)
• 8b92f61 feat: adding json, yaml and toml sources (#211)
• 0a00678 Improve docs (#225)
• 40230ab Fix for JSON on optional nested types. (#217)
• a6f6fa4 Ensure extra='forbid' is enforced in DotEnvSettingsSource when env_prefix is ...
• cc6dc25 Add support for parsing environment "None" strings to None. (#206)
• 9c26c1e Fix typo in explode_env_vars() docstring (#207)
• 2784a70 Allow nested env var source to override nested init source. (#204)
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[shtlrs]

I've updated the config tests to make sure we can rely on the unit test upon bumping pydantic PRs

[dependabot]

A newer version of pydantic-settings exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

[wookie184]

I don't really understand the purpose of the added changes. What was wrong with the existing test? Why is the change in this PR? Why does whether it's running in CI need to be relevant to the test here?

[shtlrs]

I don't really understand the purpose of the added changes. What was wrong with the existing test?

The existing test dates back to when where we loaded the config from the yaml file, it's not relevant anymore

sections = (
            cls
            for (name, cls) in inspect.getmembers(constants)
            if hasattr(cls, "section") and isinstance(cls, type)
        )

This evaluates to nothing, so the test isn't doing anything.

Why is the change in this PR?

I figured i'd contextualize testing pydantic settings along with this PR since it bumps that package, and I didn't want to test manually each time so I added it here. It doesn't really matter whether it's here or in a separate PR.

Why does whether it's running in CI need to be relevant to the test here?

Because I wanted to test that pydantic loads variables correctly from the environment, not the env file. And I can't guarantee the value of an env variable on contribs machine if they ever run tests, which will cause a failure when such a variable doesn't exist :)

[wookie184]

The existing test dates back to when where we loaded the config from the yaml file, it's not relevant anymore

Makes sense, thanks 👍

Because I wanted to test that pydantic loads variables correctly from the environment, not the env file. And I can't guarantee the value of an env variable on contribs machine if they ever run tests, which will cause a failure when such a variable doesn't exist :)

It's not ideal for a test to behave differently in CI versus locally. Can we use os.environ to set an environment variable in the test? Potentially also patching os.environ could work: https://adamj.eu/tech/2020/10/13/how-to-mock-environment-variables-with-pythons-unittest/.

I figured i'd contextualize testing pydantic settings along with this PR since it bumps that package, and I didn't want to test manually each time so I added it here. It doesn't really matter whether it's here or in a separate PR.

I think in general keeping PRs as atomic as possible is best since it makes them easier to review, keeps discussion in the PR focussed on one thing, and prevents blocking one thing on another. It's fine to leave it here though.

[shtlrs]

@dependabot recreate

[dependabot]

Superseded by #2934.

[shtlrs]

@wookie184 I've closed this and Merged a new PR bump.
I'll update the tests in a separate PR