Skip to content

chore(deps): update dependency mypy-extensions to v1.2.0 - #316

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/mypy-extensions-1.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/mypy-extensions-1.x

Conversation

@renovate

@renovate renovate Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
mypy-extensions ==1.1.0 → ==1.2.0 age adoption passing confidence

Release Notes

python/mypy_extensions (mypy-extensions)

v1.2.0

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. This is a one-line minor version bump of a transitive dev dependency.

What was reviewed:

  • requirements-dev.txt: only the mypy-extensions pin changes, from 1.1.0 to 1.2.0. Its # via mypy annotation and the other pins are untouched, so the file still looks like pip-compile output.
  • mypy 2.4.1 has an open-ended lower bound on mypy-extensions (>=1.0.0), so 1.2.0 satisfies it.
Extended reasoning...

The change touches one line in requirements-dev.txt. It bumps mypy-extensions, a dev-only transitive dependency of mypy, from 1.1.0 to 1.2.0. No source code, runtime requirements or CI configuration change, and the change touches no security-sensitive surface. The repository has no CODEOWNERS file, and the PR timeline shows no reviewer objections. The approval rests on the change being small, mechanical and limited to dev tooling.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants