Skip to content

Use shared localization tooling from vscode-python-ci - #2010

Merged
Eduardo Villalpando Mello (edvilme) merged 1 commit into
mainfrom
localization-ci
Nov 13, 2026
Merged

Eduardo Villalpando Mello (edvilme) merged 1 commit into
mainfrom
localization-ci

Conversation

@edvilme

Copy link
Copy Markdown
Contributor

Summary

Follow the successful Black Formatter pilot: microsoft/vscode-black-formatter#844 and https://github.com/microsoft/vscode-black-formatter/actions/runs/43083946783.

  • Use microsoft/vscode-python-ci/actions/localization@f078b68e968b56e0a22d6cf803bb241a6b094994 for English submission.
  • Point localizationTools in stable and pre-release Azure definitions to the same repository and SHA.
  • Preserve all caller inputs, credentials, source paths, runtime/submodule configuration, triggers, concurrency, translation data/branch, resource aliases, service connections, build and publishing settings.

The shared helper remains at scripts/localization.py. No Azure-template rewrite, package/version change, dependency change or release is included. Existing App ID/private key stay in the caller; no credential migration is needed. The implementation was merged in microsoft/vscode-python-ci#14.

Validation

  • Prettier passed for all three changed YAML files.
  • Parsed comparison confirms exactly five reference lines changed across three files; all other YAML is identical.
  • Both legacy input contracts and helper CLI argument declarations match the destination, and every caller input is supported.
  • CRLF-aware staged whitespace check passed, preserving existing tracked line endings.
  • Shared implementation passed its Linux/Windows x Python 3.10/3.13 matrix. Black's live GitHub workflow passed using this exact pin.
  • Extension runtime tests were not run for this reference-only change. This repository's GitHub CI runs on the PR.

Follow-up validation

  • Run this caller's English submission workflow and verify a synchronized rerun is a no-op.
  • Confirm Github-Pylance can read the pinned vscode-python-ci repository.
  • Validate translation import in a controlled non-publishing Azure build and inspect the VSIX for all 14 configured locales. Ensure GitHub tag/release side effects are disabled or gated before queuing.

Black's GitHub result does not prove Azure packaging or this caller's live credentials. No live localization submission or Azure release has been queued by this PR.

Rollback

Restore the action to microsoft/vscode-common-python-lsp/.github/actions/localization@6b4a3573e7e7a9fe1e468e129544432278aec2d6 and both localizationTools resources to microsoft/vscode-common-python-lsp@6b4a3573e7e7a9fe1e468e129544432278aec2d6 together. Old tooling is retained.

Pin GitHub localization and stable/pre-release Azure tooling to the same reviewed shared-action merge while preserving caller configuration.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 956d3afd-ae0b-486c-a60c-3a6276c23213
@edvilme Eduardo Villalpando Mello (edvilme) added the debt Code quality issues label Nov 11, 2026
@StellaHuang95

Stella Huang (StellaHuang95) commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

🔒 Automated review in progress — Stella Huang (@StellaHuang95) is auto-reviewing this PR.

@StellaHuang95

Copy link
Copy Markdown
Contributor

Reviewed commit: 7f941387b037fac9de4b544b6b91a457c3f6c6e1

Result: 🔴 could-not-verify

Verification details

Verification: 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 CLI is not installed or is not on PATH.

Test runs: none recorded.

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.

Approved via Review Center.

@StellaHuang95 Stella Huang (StellaHuang95) added the review-auto:approved Automated review: no blocking findings (approval posted). label Nov 11, 2026
@edvilme Eduardo Villalpando Mello (edvilme) added the no-merge PR is currently blocked from merging label Nov 11, 2026
@edvilme

Copy link
Copy Markdown
Contributor Author

Added no-merge tag. This should be merged after today's release

@rchiodo Rich Chiodo (rchiodo) 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.

Approved via Review Center.

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
@edvilme Eduardo Villalpando Mello (edvilme) removed the no-merge PR is currently blocked from merging label Nov 13, 2026
@edvilme
Eduardo Villalpando Mello (edvilme) merged commit a32fb10 into main Nov 13, 2026
123 of 125 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

debt Code quality issues review-auto:approved Automated review: no blocking findings (approval posted).

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants