Skip to content

Bump next-* tool version targets: pylint 4.0.6, mypy 2.1.0, pyright 1.1.411#47920

Merged
JennyPng merged 2 commits into
Azure:mainfrom
JennyPng:0726-vnext-bumps
Jul 8, 2026
Merged

Bump next-* tool version targets: pylint 4.0.6, mypy 2.1.0, pyright 1.1.411#47920
JennyPng merged 2 commits into
Azure:mainfrom
JennyPng:0726-vnext-bumps

Conversation

@JennyPng

@JennyPng JennyPng commented Jul 7, 2026

Copy link
Copy Markdown
Member

Bumps the next-* version targets for pylint, mypy, and pyright to the latest available releases on PyPI. The current pinned versions are unchanged this round because they already match the previous next-* targets.

Changes

  • pylint: current 4.0.4 (unchanged) — next 4.0.4 → 4.0.6
  • mypy: current 1.19.1 (unchanged) — next 1.19.1 → 2.1.0
  • pyright: current 1.1.407 (unchanged) — next 1.1.407 → 1.1.411

Files updated

  • eng/tools/azure-sdk-tools/azpysdk/pylint.pyNEXT_PYLINT_VERSION
  • eng/tools/azure-sdk-tools/azpysdk/mypy.pyNEXT_MYPY_VERSION
  • eng/tools/azure-sdk-tools/azpysdk/pyright.pyNEXT_PYRIGHT_VERSION
  • doc/analyze_check_versions.md — Next Version column and merge date (2026-10-05)

Notes

  • Python 3.10 (our lowest supported version) is supported by all three new next-* targets (verified against 3.10 wheels; mypy 2.1.0 ships a cp310 wheel).
  • mypy is a major version bump (1.x → 2.1.0); the weekly next-mypy job may surface new findings.

Verification

  • Weekly next-pylint CI passes for core packages
  • Weekly next-mypy CI passes for core packages
  • Weekly next-pyright CI passes for core packages

@JennyPng JennyPng changed the title bump next Bump next-* tool version targets: pylint 4.0.6, mypy 2.1.0, pyright 1.1.411 Jul 7, 2026
@JennyPng
JennyPng marked this pull request as ready for review July 7, 2026 21:17
@JennyPng
JennyPng requested review from a team and danieljurek as code owners July 7, 2026 21:17
Copilot AI review requested due to automatic review settings July 7, 2026 21:17

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the next-* target versions used by azpysdk for linting and type-checking tools (pylint, mypy, pyright), and updates the corresponding documentation table that tracks current vs next tool versions and planned merge dates.

Changes:

  • Bump NEXT_PYLINT_VERSION to 4.0.6 (current pinned stays 4.0.4).
  • Bump NEXT_MYPY_VERSION to 2.1.0 (current pinned stays 1.19.1).
  • Bump NEXT_PYRIGHT_VERSION to 1.1.411 (current pinned stays 1.1.407).

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File Description
eng/tools/azure-sdk-tools/azpysdk/pylint.py Updates next-pylint target version constant used when --next is enabled.
eng/tools/azure-sdk-tools/azpysdk/mypy.py Updates next-mypy target version constant used when --next is enabled.
eng/tools/azure-sdk-tools/azpysdk/pyright.py Updates next-pyright target version constant used when --next is enabled.
doc/analyze_check_versions.md Updates “Next Version” values and merge dates for the three tools (table formatting currently needs a small fix).

Comment thread doc/analyze_check_versions.md
@JennyPng
JennyPng merged commit ac070cb into Azure:main Jul 8, 2026
30 of 33 checks passed
@JennyPng
JennyPng deleted the 0726-vnext-bumps branch July 8, 2026 22:02
mzhongl524 pushed a commit to mzhongl524/typespec that referenced this pull request Jul 17, 2026
… 1.1.411, pylint-guidelines-checker 0.5.9 (microsoft#11197)

bumping check versions
Azure/azure-sdk-for-python#47920

also bump pylint guideline checker version from 0.5.2 to the latest
0.5.9

updates emitter for new rules
- disable `no-cross-package-private-import` because it has false
positives
- suppress `docstring-keyword-should-match-keyword-only` for now,
because we have some params like `api_version` that are in the docstring
but not explicit parameters and only in kwargs
- build keyword param lines for docstring
- suppress `docstring-missing-param` check which flags undocumented args
in signatures like `init(self, *args, **kwargs)`
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.

3 participants