next-version-update
Next Version Update
Promote next-* tool versions (pylint, mypy, pyright) to become the current pinned versions, update all relevant configuration files, and set new next-* targets for tracking upcoming releases.
Overview
The repository pins specific versions of pylint, mypy, and pyright and runs weekly next-* jobs to proactively detect compatibility issues with upcoming versions. When CI confirms the next-* versions are clean, this skill promotes them to become the current pinned versions.
Required cross-repo check (do not skip): After updating
azure-sdk-for-python, you must also check whether matching updates are required in both azure-sdk-tools and Microsoft/TypeSpec. Treat the version bump as complete only after those repositories are reviewed and, when needed, PRs are opened.
Files updated in azure-sdk-for-python:
eng/tools/azure-sdk-tools/azpysdk/pylint.py–PYLINT_VERSIONconstanteng/tools/azure-sdk-tools/azpysdk/mypy.py–MYPY_VERSIONconstanteng/tools/azure-sdk-tools/azpysdk/pyright.py–PYRIGHT_VERSIONconstantpylintrc– root pylintrc used by the current pylint versioneng/pylintrc– pylintrc used by thenext-pylintjob (update for new next version)doc/analyze_check_versions.md– version table documentation