Skip to content

Bump mypy from 1.16.1 to 1.19.1#63

Merged
docktermj merged 2 commits intomainfrom
dependabot/pip/mypy-1.19.1
Feb 16, 2026
Merged

Bump mypy from 1.16.1 to 1.19.1#63
docktermj merged 2 commits intomainfrom
dependabot/pip/mypy-1.19.1

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 16, 2026

Bumps mypy from 1.16.1 to 1.19.1.

Changelog

Sourced from mypy's changelog.

Mypy 1.19.1

  • Fix noncommutative joins with bounded TypeVars (Shantanu, PR 20345)
  • Respect output format for cached runs by serializing raw errors in cache metas (Ivan Levkivskyi, PR 20372)
  • Allow types.NoneType in match cases (A5rocks, PR 20383)
  • Fix mypyc generator regression with empty tuple (BobTheBuidler, PR 20371)
  • Fix crash involving Unpack-ed TypeVarTuple (Shantanu, PR 20323)
  • Fix crash on star import of redefinition (Ivan Levkivskyi, PR 20333)
  • Fix crash on typevar with forward ref used in other module (Ivan Levkivskyi, PR 20334)
  • Fail with an explicit error on PyPy (Ivan Levkivskyi, PR 20389)

Acknowledgements

Thanks to all mypy contributors who contributed to this release:

  • A5rocks
  • BobTheBuidler
  • bzoracler
  • Chainfire
  • Christoph Tyralla
  • David Foster
  • Frank Dana
  • Guo Ci
  • iap
  • Ivan Levkivskyi
  • James Hilton-Balfe
  • jhance
  • Joren Hammudoglu
  • Jukka Lehtosalo
  • KarelKenens
  • Kevin Kannammalil
  • Marc Mueller
  • Michael Carlstrom
  • Michael J. Sullivan
  • Piotr Sawicki
  • Randolf Scholz
  • Shantanu
  • Sigve Sebastian Farstad
  • sobolevn
  • Stanislav Terliakov
  • Stephen Morton
  • Theodore Ando
  • Thiago J. Barbalho
  • wyattscarpenter

I’d also like to thank my employer, Dropbox, for supporting mypy development.

Mypy 1.18

We’ve just uploaded mypy 1.18.1 to the Python Package Index (PyPI). Mypy is a static type checker for Python. This release includes new features, performance

... (truncated)

Commits

Dependabot compatibility score

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 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)

Resolves #20414
Resolves #20372
Resolves #20389
Resolves #20384
Resolves #20383
Resolves #20371
Resolves #20345
Resolves #20323
Resolves #20333

Bumps [mypy](https://github.com/python/mypy) from 1.16.1 to 1.19.1.
- [Changelog](https://github.com/python/mypy/blob/master/CHANGELOG.md)
- [Commits](python/mypy@v1.16.1...v1.19.1)

---
updated-dependencies:
- dependency-name: mypy
  dependency-version: 1.19.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Feb 16, 2026
@dependabot dependabot bot requested a review from a team as a code owner February 16, 2026 21:01
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Feb 16, 2026
@github-actions
Copy link

🤖 Claude Code Review


Code Review: mypy Version Bump (1.16.1 → 1.19.1)

Summary

This PR updates the mypy dependency from version 1.16.1 to 1.19.1 in development-requirements.txt. This is a straightforward dependency update with no code changes.

Detailed Review Against Checklist

✅ Code Quality

  • ✅ Code follows style guide: Not applicable - no code changes
  • ✅ No commented-out code: Not applicable - no code changes
  • ✅ Meaningful variable names: Not applicable - no code changes
  • ✅ DRY principle followed: Not applicable - no code changes
  • ✅ Identify Defects: No defects identified. This is a minor version bump of a development dependency (static type checker). The update is from 1.16.1 to 1.19.1, which represents 3 minor versions. This is a reasonable update that should bring bug fixes and potentially new type checking features.
  • ✅ Project memory (.claude/CLAUDE.md): No project-specific Claude configuration found, so no additional review criteria to consider.

✅ Testing

  • ✅ Unit tests: Not required - dependency update only
  • ✅ Integration tests: Not required - dependency update only
  • ✅ Edge cases covered: Not applicable
  • ✅ Test coverage > 80%: Not applicable - no new code

Note: While new tests aren't required for a dependency update, it would be good practice to verify that existing type checks still pass with the new mypy version. The CI pipeline should validate this.

⚠️ Documentation

  • ✅ Readme updated: Not needed - dependency updates don't require README changes
  • ✅ API docs updated: Not needed - no API changes
  • ✅ Inline comments: Not applicable - no code changes
  • ❌ CHANGELOG.md updated: The CHANGELOG.md (development-requirements.txt:9) should be updated to reflect this dependency update. Currently shows placeholder entries like "Thing 5", "Thing 4" but no mention of the mypy update.

Recommendation: Add an entry under the [Unreleased] section:

## [Unreleased]

- Updated mypy from 1.16.1 to 1.19.1
  • ✅ Markdown formatting: The existing CHANGELOG.md follows CommonMark specification and appears properly formatted.

✅ Security

  • ✅ No hardcoded credentials: None found
  • ✅ Input validation: Not applicable
  • ✅ Proper error handling: Not applicable
  • ✅ No sensitive data in logs: Not applicable
  • ✅ No license files (.lic) or AQAAAD strings: None found in the diff

Final Assessment

Overall: Minor issue found

This is a clean dependency update with only one minor issue:

Required Action:

  • ❌ Update CHANGELOG.md to document the mypy version bump (development-requirements.txt:9)

Recommendations:

  • Ensure CI passes with the new mypy version, as newer versions may have stricter type checking rules
  • Consider reviewing any new mypy warnings or errors that may surface with version 1.19.1

The change itself is safe and appropriate for a development dependency update.

Automated code review analyzing defects and coding standards

@docktermj docktermj self-assigned this Feb 16, 2026
@docktermj docktermj enabled auto-merge (squash) February 16, 2026 21:08
@docktermj docktermj merged commit a961205 into main Feb 16, 2026
18 checks passed
@docktermj docktermj deleted the dependabot/pip/mypy-1.19.1 branch February 16, 2026 21:08
@github-actions
Copy link

🤖 Claude Code Review

Code Review: Dependency Update (mypy 1.16.1 → 1.19.1)

Summary

This PR updates the mypy development dependency from version 1.16.1 to 1.19.1 in development-requirements.txt.


Detailed Review

✅ Code Quality

  • Code follows style guide: This is a dependency version update in a requirements file - no code style issues.
  • No commented-out code: None present.
  • Meaningful variable names: N/A - dependency update only.
  • DRY principle followed: N/A - dependency update only.
  • Identify Defects: No defects, logic errors, or security vulnerabilities introduced. This is a straightforward dependency version bump.
  • Project memory (.claude/CLAUDE.md): No project-specific Claude configuration found in the repository root. (Note: There is a build-resources/.claude/CLAUDE.md but that appears to be for build tooling, not this project)

⚠️ Testing

  • ⚠️ Unit tests for new functions: N/A - dependency update only, but mypy version updates can affect type checking results.
  • ⚠️ Integration tests: N/A
  • ⚠️ Edge cases covered: N/A
  • ⚠️ Test coverage > 80%: Unable to verify from diff, but this change should not affect coverage.

Recommendation: Ensure that the updated mypy version runs successfully and doesn't introduce new type errors. The CI/CD pipeline should validate this.

❌ Documentation

  • CHANGELOG.md updated: The CHANGELOG.md file at /home/runner/work/mapper-npi/mapper-npi/CHANGELOG.md:9-12 shows the [Unreleased] section with placeholder entries ("Thing 5", "Thing 4") but does not document this mypy version bump.
  • Readme updated if needed: N/A - dependency updates typically don't require README changes.
  • API docs updated: N/A
  • Inline comments: N/A
  • Markdown formatting: The CHANGELOG.md follows CommonMark and appears properly formatted.

Action Required: Update CHANGELOG.md to document this dependency update:

## [Unreleased]

- Updated mypy from 1.16.1 to 1.19.1

✅ Security

  • No hardcoded credentials: None present.
  • Input validation: N/A
  • Proper error handling: N/A
  • No sensitive data in logs: N/A
  • No license files (.lic): No .lic files found in the repository.
  • No AQAAAD strings: The string "AQAAAD" appears only in documentation/configuration files (cspell dictionary, prompt templates) as part of the security checklist itself, not as actual license data.

Overall Assessment

Status: ⚠️ Requires Minor Changes

Issues to Address

  1. CHANGELOG.md not updated (/home/runner/work/mapper-npi/mapper-npi/CHANGELOG.md:9)
    • The dependency update should be documented in the [Unreleased] section
    • Remove placeholder entries ("Thing 5", "Thing 4") and add the actual change

Recommendations

  1. Verify that CI/CD passes with the new mypy version (1.19.1 may have stricter type checking)
  2. Consider if this is a patch, minor, or major version bump from mypy's perspective and ensure compatibility

Severity

  • Low - The only issue is missing changelog documentation, which is easily fixed.

Automated code review analyzing defects and coding standards

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

Labels

dependencies Pull requests that update a dependency file python Pull requests that update python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant