Zipper Tools

Pydantic Migration Guides

Why Config.fields is a manual-review case in Pydantic v2

Config.fields was removed in Pydantic v2, so this is not a simple model_config rename.

Start here

The safe first move

Treat Config.fields as manual review. It was removed in Pydantic v2, so the migration depends on what behavior the model actually needs.

Stop before automation when: Choosing the right replacement behavior per model. Files that also combine supported and unsupported Config keys.

Target shape

# manual review required
# Config.fields was removed in Pydantic v2

Repo fit check

Want to know if your repo has this pattern?

Run the matching scanner locally first. Read the free findings and manual alternatives; consider paid cleanup only if supported patterns repeat enough to justify the price.

  • Local scan; no repository upload.
  • Supported findings are separated from manual-review findings.
  • Buy only when the repeated pattern is worth automating.
Run the Pydantic scan first View example report See when to buy 
Example scan summary
supported_findings: 38
manual_review_findings: 6
files_uploaded: 0
confidence: reviewable

Why this page exists

Why Config.fields is a manual-review case in Pydantic v2

Some Config keys have a direct rename. Config.fields does not.

Direct answer

What changes

Treat Config.fields as manual review. It was removed in Pydantic v2, so the migration depends on what behavior the model actually needs.

Example

Before and after

Before

class Config:
    fields = {"name": {"alias": "full_name"}}

After

# manual review required
# Config.fields was removed in Pydantic v2

Decision path

If this repeats across the repo, open the evaluation pages next.

The cleanup pack is strongest when the repo still uses direct pydantic imports and a clean validator/settings/config subset.

  • The repo has direct pydantic or pydantic.v1 imports, BaseSettings usage, safe Config blocks, or simple validators.
  • The migration pain is repetitive v1-to-v2 cleanup, not a custom semantic rewrite.
  • If the scan output is ambiguous, review its findings and upstream guidance. Do not buy expecting unsupported cases to be resolved.

Typical symptoms

  • Teams expect every Config key to become a simple model_config entry.
  • The porter needs to stop cleanly on removed keys instead of bluffing through them.
  • Reviewers want a clear list of which files still need manual follow-up.

What the product covers

  • Explicit findings for removed Config keys like fields.
  • Cross-links to the supported Config-to-model_config page.
  • Repo-fit guidance before buying the porter.

Manual-review boundary

  • Choosing the right replacement behavior per model.
  • Files that also combine supported and unsupported Config keys.
  • Any config logic that depends on project-specific validation behavior.

Keep the migration narrow

Use the exact-problem guides as a triage layer, then decide whether the repo is inside the supported subset.

FAQ

Fast answers before you decide

What is the safest fix for Config fields removed pydantic v2?

Treat Config.fields as manual review. It was removed in Pydantic v2, so the migration depends on what behavior the model actually needs.

Can Config fields removed pydantic v2 be automated?

Automate only the supported subset: Explicit findings for removed Config keys like fields. Cross-links to the supported Config-to-model_config page. Repo-fit guidance before buying the porter. Keep these cases in manual review: Choosing the right replacement behavior per model. Files that also combine supported and unsupported Config keys. Any config logic that depends on project-specific validation behavior.

When should I buy Pydantic v1 to v2 Migration Cleanup Pack?

Use Pydantic v1 to v2 Migration Cleanup Pack only when this pattern repeats across enough files that manual cleanup is still costly. Use the free report and upstream guide to evaluate fit. Buy only if repeated supported edits justify the price; no paid assessment is required.

Purchase fit

Choose the lowest-risk next step.

One matching page is not enough by itself. Run the local scan, then buy only when the same supported pattern appears often enough to matter.

Buy if

  • The repo has direct pydantic or pydantic.v1 imports, BaseSettings usage, safe Config blocks, or simple validators.
  • The migration pain is repetitive v1-to-v2 cleanup, not a custom semantic rewrite.
  • The team accepts manual-review findings for alias-heavy imports and signature-heavy validators.

What the workflow includes

  • Installable local CLI workflow, not a hosted black box.
  • Supported validator, settings, import, and config rewrites.
  • Demo report, public proof, coverage notes, rollback checklist, and buyer terms.

Before checkout

  • Stripe Checkout handles secure payment and receipts.
  • Download your purchased ZIP after payment.
  • Runs locally; no hosted API, repo upload, or production credentials needed.
  • The free report includes the evidence needed to evaluate fit. Paid summary and template add-ons are optional.
  • 14-day refund review for published-scope or delivery mismatches.
Run the Pydantic scan first

Explore the details