Repository navigation
Allow English fallback during localization release imports - #1140
Bill Schnurr (bschnurr) merged 3 commits into
Conversation
Pin submission and release imports to the same reviewed shared revision. Untranslated handbacks no longer block packaging; required locale tables and structural checks remain. Co-authored-by: Copilot <[email protected]>
|
🔒 Automated review in progress — Rich Chiodo (@rchiodo) is auto-reviewing this PR. |
|
Reviewed commit: Result: Verification detailsVerification: Automated verification is best effort. The PR author remains responsible for testing. Summary: Formatting passed for all three changed YAML files, and executable parsed-YAML checks passed for the workflow and both release callers. The checks confirmed matching localization pins, GitHub template resources, and preserved build/publication settings. Offline dependency preparation succeeded; initial discovery could not access Git metadata in the container. No tests were added, and external localization imports and Azure expansion were not executed, so verification is partial. **Reviewer dependency follow-up (nonblocking):** Suggest a separate PR adding `prettier ^3.0.3` to the official reviewer dependency declarations, using `package.json` as the dependency/version evidence. Do not automatically create that PR. This is reviewer environment maintenance, not a required change to the reviewed PR. Test runs: 3 passed, 1 failed, 1 not run
|
Rich Chiodo (rchiodo)
left a comment
There was a problem hiding this comment.
Approved via Review Center.
Switch both release resources to microsoft/pylance-eng through Github-Pylance while preserving release settings. Co-authored-by: Copilot <[email protected]>
53585bc
Dependency: microsoft/vscode-common-python-lsp#127
Pin the localization action and both release import resources to 6b4a3573e7e7a9fe1e468e129544432278aec2d6. This allows untranslated strings, including wholly untranslated tables, to retain English rather than fail packaging. Missing/empty/malformed/incomplete locale tables remain errors. Update the documented policy; preserve dev translation branch, Pylance-Eng main, publication defaults, and all build/release settings.
Validation: actual-YAML caller guards, formatting, and Azure preview expansion passed. Shared tests/lint passed; real isort dev import produces all 28 locale files with English fallback. Environments' native pipelines remain disabled; exact YAML expansion was verified through an enabled definition. No release builds queued or publication performed. Merge the shared dependency before this consumer pin update.
GitHub pipeline templates
microsoft/pylance-engon GitHub instead ofDevDiv/Pylance-Engin both stable and pre-release template resources, through the existingGithub-Pylanceservice connection.refs/heads/main, template paths, build steps, localization pins, release settings, and publication defaults. Document service-connection access for template, translation, and shared-tooling resources.Verification
publishExtension: false.These are preview expansions, not full sibling build runs. No new release builds were queued, no extension was published, and no PR was merged.