Do not use deprecated methods as default field values

[Viicos]

Change Summary

Fixes #11912.

Related issue number

Checklist

• The pull request title is a good summary of the changes - it will be used in the changelog
• Unit tests for the changes exist
• Tests pass on CI
• Documentation reflects the changes where applicable
• My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

[cloudflare-workers-and-pages]

Deploying pydantic-docs with    Cloudflare Pages

Latest commit:	58a4ea2
Status:	⚡️  Build in progress...

View logs

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
pydantic
types.py					1171
pydantic/_internal
_fields.py
Project Total

This report was generated by python-coverage-comment-action

[codspeed-hq]

CodSpeed Performance Report

Merging #11914 will not alter performance

_{Comparing deprecated-method-defaults (58a4ea2) with main (f0e1d04)}

Summary

✅ 46 untouched benchmarks

[yiphei]

@Viicos i didnt see this fix being in the latest release. how do you your releases work? just curious, also because I want to get this fix into my dev environment

[Viicos]

This will be released in 2.12, which we'll push during the summer.

[yiphei]

@Viicos to avoid asking you in the future, how can i find out which release a fix will be pushed to?

[Viicos]

If you check the commit that was created to merge the PR to main (in this case 638d047), you can check the tags that include that commit. For this one, because it wasn't included in any release yet, it is empty:

This is how it looks for a commit that was released:

Alternatively, lookup the changelog for the PR number.