Bump pydantic from 1.8.2 to 1.9.0

[dependabot]

Bumps pydantic from 1.8.2 to 1.9.0.

Release notes

Sourced from pydantic's releases.

v1.9.0 (2021-12-31)

Thank you to pydantic's sponsors: @​sthagen, @​timdrijvers, @​toinbis, @​koxudaxi, @​ginomempin, @​primer-io, @​and-semakin, @​westonsteimel, @​reillysiemens, @​es3n1n, @​jokull, @​JonasKs, @​Rehket, @​corleyma, @​daddycocoaman, @​hardbyte, @​datarootsio, @​jodal, @​aminalaee, @​rafsaf, @​jqueguiner, @​chdsbd, @​kevinalh, @​Mazyod, @​grillazz, @​JonasKs, @​simw, @​leynier, @​xfenix for their kind support.

Highlights

• add python 3.10 support, #2885 by @​PrettyWood
• Discriminated unions, #619 by @​PrettyWood
• Config.smart_union for better union logic, #2092 by @​PrettyWood
• Binaries for Macos M1 CPUs, #3498 by @​samuelcolvin
• Complex types can be set via nested environment variables, e.g. foo___bar, #3159 by @​Air-Mark
• add a dark mode to pydantic documentation, #2913 by @​gbdlin
• Add support for autocomplete in VS Code via __dataclass_transform__, #2721 by @​tiangolo
• Add "exclude" as a field parameter so that it can be configured using model config, #660 by @​daviskirk

v1.9.0 (2021-12-31) Changes

• Apply update_forward_refs to Config.json_encodes prevent name clashes in types defined via strings, #3583 by @​samuelcolvin
• Extend pydantic's mypy plugin to support mypy versions 0.910, 0.920, 0.921 & 0.930, #3573 & #3594 by @​PrettyWood, @​christianbundy, @​samuelcolvin

v1.9.0a2 (2021-12-24) Changes

• support generic models with discriminated union, #3551 by @​PrettyWood
• keep old behaviour of json() by default, #3542 by @​PrettyWood
• Removed typing-only __root__ attribute from BaseModel, #3540 by @​layday
• Build Python 3.10 wheels, #3539 by @​mbachry
• Fix display of extra fields with model __repr__, #3234 by @​cocolman
• models copied via Config.copy_on_model_validation always have all fields, #3201 by @​PrettyWood
• nested ORM from nested dictionaries, #3182 by @​PrettyWood
• fix link to discriminated union section by @​PrettyWood

v1.9.0a1 (2021-12-18) Changes

• Add support for Decimal-specific validation configurations in Field(), additionally to using condecimal(), to allow better support from editors and tooling, #3507 by @​tiangolo
• Add arm64 binaries suitable for MacOS with an M1 CPU to PyPI, #3498 by @​samuelcolvin
• Fix issue where None was considered invalid when using a Union type containing Any or object, #3444 by @​tharradine
• When generating field schema, pass optional field argument (of type pydantic.fields.ModelField) to __modify_schema__() if present, #3434 by @​jasujm
• Fix issue when pydantic fail to parse typing.ClassVar string type annotation, #3401 by @​uriyyo
• Mention Python >= 3.9.2 as an alternative to typing_extensions.TypedDict, #3374 by @​BvB93
• Changed the validator method name in the Custom Errors example to more accurately describe what the validator is doing; changed from name_must_contain_space to value_must_equal_bar, #3327 by @​michaelrios28
• Add AmqpDsn class, #3254 by @​kludex
• Always use Enum value as default in generated JSON schema, #3190 by @​joaommartins
• Add support for Mypy 0.920, #3175 by @​christianbundy
• validate_arguments now supports extra customization (used to always be Extra.forbid), #3161 by @​PrettyWood

... (truncated)

Changelog

Sourced from pydantic's changelog.

v1.9.0 (2021-12-31)

Thank you to pydantic's sponsors: @​sthagen, @​timdrijvers, @​toinbis, @​koxudaxi, @​ginomempin, @​primer-io, @​and-semakin, @​westonsteimel, @​reillysiemens, @​es3n1n, @​jokull, @​JonasKs, @​Rehket, @​corleyma, @​daddycocoaman, @​hardbyte, @​datarootsio, @​jodal, @​aminalaee, @​rafsaf, @​jqueguiner, @​chdsbd, @​kevinalh, @​Mazyod, @​grillazz, @​JonasKs, @​simw, @​leynier, @​xfenix for their kind support.

Highlights

• add python 3.10 support, #2885 by @​PrettyWood
• Discriminated unions, #619 by @​PrettyWood
• Config.smart_union for better union logic, #2092 by @​PrettyWood
• Binaries for Macos M1 CPUs, #3498 by @​samuelcolvin
• Complex types can be set via nested environment variables, e.g. foo___bar, #3159 by @​Air-Mark
• add a dark mode to pydantic documentation, #2913 by @​gbdlin
• Add support for autocomplete in VS Code via __dataclass_transform__, #2721 by @​tiangolo
• Add "exclude" as a field parameter so that it can be configured using model config, #660 by @​daviskirk

v1.9.0 (2021-12-31) Changes

• Apply update_forward_refs to Config.json_encodes prevent name clashes in types defined via strings, #3583 by @​samuelcolvin
• Extend pydantic's mypy plugin to support mypy versions 0.910, 0.920, 0.921 & 0.930, #3573 & #3594 by @​PrettyWood, @​christianbundy, @​samuelcolvin

v1.9.0a2 (2021-12-24) Changes

• support generic models with discriminated union, #3551 by @​PrettyWood
• keep old behaviour of json() by default, #3542 by @​PrettyWood
• Removed typing-only __root__ attribute from BaseModel, #3540 by @​layday
• Build Python 3.10 wheels, #3539 by @​mbachry
• Fix display of extra fields with model __repr__, #3234 by @​cocolman
• models copied via Config.copy_on_model_validation always have all fields, #3201 by @​PrettyWood
• nested ORM from nested dictionaries, #3182 by @​PrettyWood
• fix link to discriminated union section by @​PrettyWood

v1.9.0a1 (2021-12-18) Changes

• Add support for Decimal-specific validation configurations in Field(), additionally to using condecimal(), to allow better support from editors and tooling, #3507 by @​tiangolo
• Add arm64 binaries suitable for MacOS with an M1 CPU to PyPI, #3498 by @​samuelcolvin
• Fix issue where None was considered invalid when using a Union type containing Any or object, #3444 by @​tharradine
• When generating field schema, pass optional field argument (of type pydantic.fields.ModelField) to __modify_schema__() if present, #3434 by @​jasujm
• Fix issue when pydantic fail to parse typing.ClassVar string type annotation, #3401 by @​uriyyo
• Mention Python >= 3.9.2 as an alternative to typing_extensions.TypedDict, #3374 by @​BvB93
• Changed the validator method name in the Custom Errors example to more accurately describe what the validator is doing; changed from name_must_contain_space to value_must_equal_bar, #3327 by @​michaelrios28
• Add AmqpDsn class, #3254 by @​kludex
• Always use Enum value as default in generated JSON schema, #3190 by @​joaommartins
• Add support for Mypy 0.920, #3175 by @​christianbundy

... (truncated)

Commits

• fbf8002 prepare for v1.9.0 release, extra change
• 5406423 prepare for v1.9.0 release
• 87da9ac apply update_forward_refs to json_encoders (#3595)
• 6f26a1c Support mypy 0.910 to 0.930 including CI tests (#3594)
• 8ef492b build(deps): bump mypy from 0.920 to 0.930 (#3573)
• 2d3d266 remove failing release step
• ef46789 add step to upload pypi files to release
• 5d6f48c prepare for v1.9.0a2
• e882277 fix: support generic models with discriminated union (#3551)
• edad0db fix: keep old behaviour of json() by default (#3542)
• 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 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)

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.txt : +0 -0
.py : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[codecov]

Codecov Report

Merging #21 (8044364) into main (9813d07) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #21   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         4           
  Lines           85        85           
  Branches         8         8           
=========================================
  Hits            85        85           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9813d07...8044364. Read the comment docs.