Conversation
Co-authored-by: l0lawrence <100643745+l0lawrence@users.noreply.github.com>
|
@copilot I only want the skill I dont want to change any files at this time |
Co-authored-by: l0lawrence <100643745+l0lawrence@users.noreply.github.com>
Done. All version/config/doc changes have been reverted (commit |
Co-authored-by: l0lawrence <100643745+l0lawrence@users.noreply.github.com>
|
Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details. Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
|
|
||
| ### 14. Update Microsoft/TypeSpec Repository (Separate PR) | ||
|
|
||
| When a **pyright version** is promoted, create a separate PR in the [Microsoft/TypeSpec](https://github.com/microsoft/typespec) repository to keep the pyright version aligned. |
There was a problem hiding this comment.
@copilot for any next-* verison update to pylint/mypy or pyright we should do this
There was a problem hiding this comment.
Updated in commit e8fc30d8. Step 14 now applies to any pylint/mypy/pyright version update — it includes search commands for each tool's version pins, a combined branch name and commit message covering all three, and a PR body listing all version changes. The Overview section is also updated to reflect this scope.
Co-authored-by: l0lawrence <100643745+l0lawrence@users.noreply.github.com>
|
Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details. Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
Introduces a reusable skill to automate future promotions of
next-*tool versions.New Skill
.github/skills/next-version-update/SKILL.md: Step-by-step runbook for promotingnext-*versions (pylint, mypy, pyright) in the future — covers CI verification (including http-client-python in Microsoft/TypeSpec and core azure-sdk-for-python packages), PyPI version lookup, all file updates in this repo, the correspondingazure-sdk-toolsPR for apiview stub generator pylintrc/requirements, and a step for creating a PR against Microsoft/TypeSpec for any pylint/mypy/pyright version update following their contribution guidelines (CLA, Rush monorepo workflow, PR template).✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.
Looks like: