Skip to content

[WIP] Update lint/type-check tooling to next-* versions#46314

Closed
Copilot wants to merge 1 commit intomainfrom
copilot/update-lint-type-check-tooling
Closed

[WIP] Update lint/type-check tooling to next-* versions#46314
Copilot wants to merge 1 commit intomainfrom
copilot/update-lint-type-check-tooling

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Apr 14, 2026

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

Original prompt

Update lint/type-check tooling in PR #46279 to the next-* versions.

Context

  • Repository: Azure/azure-sdk-for-python
  • Pull request: next-* swap #46279 ("next-* swap")
  • Goal: update pylint, mypy, and any related lint/type-check dependencies/config ("pylint/mytpy etc") so CI uses the next-* versions consistently.

What to do

  1. Check the repo’s dependency management files (e.g., requirements*.txt, pyproject.toml, setup.cfg, tox.ini, noxfile.py, eng/, scripts/, CI workflow YAMLs) and identify where pylint, mypy, and other linting/type-checking tools are pinned.
  2. Update those pins to the appropriate next-* equivalents used by this repo (e.g., packages named like pylint-next, mypy-next, or similarly named pre-release / next-channel packages used by Azure SDK tooling). Ensure versions align with the repo’s conventions.
  3. Update any configuration or invocation that refers to the old tool package names/entrypoints if needed.
  4. Run/adjust the relevant CI job configs so they install and run the updated tooling.
  5. Ensure the PR remains green: fix any issues caused by tool upgrades (new warnings/errors, config changes, plugin compatibility, etc.).
  6. Add/adjust changelog/notes only if this repo’s conventions require it for tooling changes.

Acceptance criteria

  • All places in the repo that install or pin lint/type-check tools are updated to the next-* versions.
  • CI and local developer flows continue to work.
  • No redundant/contradictory pins remain.
  • Changes are committed to the existing PR next-* swap #46279.

Notes

  • The user specifically called out "pylint/mytpy etc" — include related tools like flake8, black, isort, pyright, ruff, pylint-azure-sdk, or any Azure SDK-specific lint plugins if they are part of the same tooling set.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: update pylint/mytpy etc to next-* versions @Azure/azure-sdk-for-python/pull/46279

Assistant: I’m currently waiting on your approval/response to proceed with making the updates in PR #46279 (switching pylint/mypy and related tooling to the appropriate next-* versions).

This pull request was created from Copilot chat.

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.

2 participants