Repository navigation
Use shared Python CI localization tooling - #1143
Merged
Merged
Conversation
Migrate the localization action and DevDiv tooling resources to the reviewed vscode-python-ci revision without changing caller inputs or release behavior. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 956d3afd-ae0b-486c-a60c-3a6276c23213
Eduardo Villalpando Mello (edvilme)
enabled auto-merge (squash)
November 11, 2026 22:07
Merged
4 tasks
Contributor
|
🔒 Automated review in progress — Rich Chiodo (@rchiodo) is auto-reviewing this PR. |
Contributor
|
Reviewed commit: Result: 🔴 Verification detailsVerification: Automated verification is best effort. The PR author remains responsible for testing. Summary: [unavailable] Container verification could not start and local execution was not authorized for this PR HEAD: Podman machine 'pyrx-automation' is not running. Test runs: none recorded. |
Rich Chiodo (rchiodo)
approved these changes
Nov 11, 2026
Rich Chiodo (rchiodo)
left a comment
Contributor
There was a problem hiding this comment.
Approved via Review Center.
Heejae Chang (heejaechang)
approved these changes
Nov 11, 2026
Eduardo Villalpando Mello (edvilme)
added a commit
to microsoft/vscode-common-python-lsp
that referenced
this pull request
Nov 12, 2026
## Summary Retire the duplicated localization automation now maintained in [microsoft/vscode-python-ci](https://github.com/microsoft/vscode-python-ci/tree/main/actions/localization). - Remove `.github/actions/localization/action.yml`, `scripts/localization.py`, and its regression tests. - Remove only the corresponding localization test/lint commands from nox; preserve all runtime package commands. - Remove the README's Shared localization automation section; shared tooling PRs [#14](microsoft/vscode-python-ci#14) and [#15](microsoft/vscode-python-ci#15) are merged. No Python/TypeScript runtime libraries, source strings, package versions, credentials, translation data, or release settings change. Existing callers pinned to historical commits remain usable; this PR does not delete tags or rewrite history. New callers must use `microsoft/vscode-python-ci/actions/localization`, and Azure tooling checkouts must use that repository with the unchanged `scripts/localization.py` interface. ## Validation - Existing Python runtime tests: **333 passed, 2 skipped**. - Black, Flake8, and isort checks passed for `noxfile.py`. - Nox session discovery and version synchronization passed. - Recorded each nox session's commands against `origin/main`: all non-localization install/test/lint commands are unchanged. - Removed paths and `git diff --check` verified. - Earlier rollout validation: two successful GitHub localization runs each for Black, Flake8, isort, Mypy, Pylint, autopep8, and the Python Environments migration branch. These were synchronized no-ops, not changed-string submissions. ## Draft / merge readiness This PR intentionally remains a draft. The default-branch GitHub caller audit still finds: - [ ] Merge [Python Environments #2010](microsoft/vscode-python-environments#2010); its `main` workflow still uses the old action. - [ ] Merge [Python Debugger #1143](microsoft/vscode-python-debugger#1143), migrating its GitHub action and stable/pre-release Azure tooling references. - [ ] Complete safe, non-publishing Azure localization import/package validation, including service-connection access to `vscode-python-ci`. GitHub tag/release creation must also be disabled; `publishExtension: false` alone is not sufficient evidence. - [ ] Review remaining Azure/release-branch/unpinned consumers before marking ready. The default-branch GitHub search is not an exhaustive audit of every caller. The two confirmed remaining workflows pin the historical `6b4a3573e7e7a9fe1e468e129544432278aec2d6` revision, so deleting the action on the new main revision does not immediately break those pinned workflows. --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 956d3afd-ae0b-486c-a60c-3a6276c23213
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Move Python Debugger localization automation to the maintained shared tooling in
microsoft/vscode-python-ci.microsoft/vscode-python-ci/actions/localization@2f06c1206c8644c50f99228a111e8c15e33e7828.localizationToolsresources at the same repository and reviewed commit.The pinned revision includes merged shared-tooling PRs #14 and #15.
This is a reference-only migration: action inputs, credentials, source paths, helper CLI arguments, triggers, concurrency, translation repository/
devbranch, service connection, extension identity, build platforms, and publishing/tag/release settings remain unchanged. No App ID/private-key rotation is required. TheGithub-Pylanceservice connection must be authorized to readmicrosoft/vscode-python-ci.Validation
origin/mainconfirm that only the action reference and the two tooling repository/ref pairs change.git diff --checkpassed.No runtime source or dependency manifests changed. Live localization dispatch and Azure import/package validation have not been run for this migration; no release pipeline was queued.
This removes a remaining old-action caller identified while drafting vscode-common-python-lsp #130. Existing App credentials and translation handbacks are retained.