Updated strings from microsoft/vscode-loc-drop@0d6c79fe1758ae1e79bf289e187c477e0bc439ec - #2412
Open
azure-pipelines[bot] wants to merge 1 commit into
Conversation
…9e187c477e0bc439ec
Contributor
Author
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
Yudhi Armyndharis (rmyndharis)
added a commit
to rmyndharis/VSCodroid
that referenced
this pull request
Sep 26, 2026
1.138.0 still targets Node 24 (remote/.npmrc names 24.18.1, the bundled Termux runtime is 24.18.0) and locks the same node-pty, @parcel/watcher and @vscode/sqlite3 that the Bionic overlay builds, so the runtime and the native addons stay as they are. - VSCODE_VERSION and VSCODE_COMMIT name the 1.138.0 tag and 7debcd0e. - 0001 and 0012 are rebased onto moved context. Their added and removed lines are unchanged, and all nineteen patches apply to 7debcd0e in order. - The workbench page's policy now trusts inline scripts by a nonce the server writes into each request, and no longer hashes bare <script> tags. The two scripts server.js adds to the page (trusted link domains and extension recommendations) would have been refused without a word, so they now carry the page's own nonce placeholder when the page uses one. - The agent host's @github/copilot-linux-arm64 moves to 1.0.84-4, whose runtime.node imports malloc_trim@GLIBC_2.17. Bionic has none at any API level, so its forwarder would abort on the first call. The glibc shim now answers it with mallopt(M_PURGE); every other strong import is exported by Bionic at API 33 or already by the shim. - @microsoft/mxc-sdk 0.8.0 replaced its glibc linux-test-proxy with a Mach-O unix-test-proxy, so that path leaves the ELF allowlist, whose stale-entry check would otherwise fail the packaging. - VSCODE_LOC_COMMIT moves to the first vscode-loc string drop after the 1.138.0 tag, microsoft/vscode-loc#2412, one commit on top of the previous pin and kept reachable by its pull request ref. vscode-loc's main has not moved since 2026-09-04: against the localize() keys in the 1.138 sources, that commit lacks about 5 percent of them and leaves about 2,800 more in English in each language. The published server-1.133.0 no longer matches patches/, so a server-1.138.0 build has to be published before an APK can be packaged.
Yudhi Armyndharis (rmyndharis)
added a commit
to rmyndharis/VSCodroid
that referenced
this pull request
Sep 26, 2026
1.138.0 still targets Node 24 (remote/.npmrc names 24.18.1, the bundled Termux runtime is 24.18.0) and locks the same node-pty, @parcel/watcher and @vscode/sqlite3 that the Bionic overlay builds, so the runtime and the native addons stay as they are. - VSCODE_VERSION and VSCODE_COMMIT name the 1.138.0 tag and 7debcd0e. - 0001 and 0012 are rebased onto moved context. Their added and removed lines are unchanged, and all nineteen patches apply to 7debcd0e in order. - The workbench page's policy now trusts inline scripts by a nonce the server writes into each request, and no longer hashes bare <script> tags. The two scripts server.js adds to the page (trusted link domains and extension recommendations) would have been refused without a word, so they now carry the page's own nonce placeholder when the page uses one. - The agent host's @github/copilot-linux-arm64 moves to 1.0.84-4, whose runtime.node imports malloc_trim@GLIBC_2.17. Bionic has none at any API level, so its forwarder would abort on the first call. The glibc shim now answers it with mallopt(M_PURGE); every other strong import is exported by Bionic at API 33 or already by the shim. - @microsoft/mxc-sdk 0.8.0 replaced its glibc linux-test-proxy with a Mach-O unix-test-proxy, so that path leaves the ELF allowlist, whose stale-entry check would otherwise fail the packaging, and LEGAL_NOTICES.md lists the thirteen binaries 0.8.0 ships. - VSCODE_LOC_COMMIT moves to the first vscode-loc string drop after the 1.138.0 tag, microsoft/vscode-loc#2412, one commit on top of the previous pin and kept reachable by its pull request ref. vscode-loc's main has not moved since 2026-09-04: against the localize() keys in the 1.138 sources, that commit lacks about 5 percent of them and leaves about 2,800 more in English in each language. The published server-1.133.0 no longer matches patches/, so a server-1.138.0 build has to be published before an APK can be packaged.
Yudhi Armyndharis (rmyndharis)
added a commit
to rmyndharis/VSCodroid
that referenced
this pull request
Sep 26, 2026
1.138.0 still targets Node 24 (remote/.npmrc names 24.18.1, the bundled Termux runtime is 24.18.0) and locks the same node-pty, @parcel/watcher and @vscode/sqlite3 that the Bionic overlay builds, so the runtime and the native addons stay as they are. - VSCODE_VERSION and VSCODE_COMMIT name the 1.138.0 tag and 7debcd0e. - 0001 and 0012 are rebased onto moved context. Their added and removed lines are unchanged, and all nineteen patches apply to 7debcd0e in order. - The workbench page's policy now trusts inline scripts by a nonce the server writes into each request, and no longer hashes bare <script> tags. The two scripts server.js adds to the page (trusted link domains and extension recommendations) would have been refused without a word, so they now carry the page's own nonce placeholder when the page uses one. - The agent host's @github/copilot-linux-arm64 moves to 1.0.84-4, whose runtime.node imports malloc_trim@GLIBC_2.17. Bionic has none at any API level, so its forwarder would abort on the first call. The glibc shim now answers it with mallopt(M_PURGE); every other strong import is exported by Bionic at API 33 or already by the shim. - @microsoft/mxc-sdk 0.8.0 replaced its glibc linux-test-proxy with a Mach-O unix-test-proxy, so that path leaves the ELF allowlist, whose stale-entry check would otherwise fail the packaging, and LEGAL_NOTICES.md lists the thirteen binaries 0.8.0 ships. - VSCODE_LOC_COMMIT moves to the first vscode-loc string drop after the 1.138.0 tag, microsoft/vscode-loc#2412, one commit on top of the previous pin and kept reachable by its pull request ref. vscode-loc's main has not moved since 2026-09-04: against the localize() keys in the 1.138 sources, that commit lacks about 5 percent of them and leaves about 2,800 more in English in each language. The published server-1.133.0 no longer matches patches/, so a server-1.138.0 build has to be published before an APK can be packaged.
This branch has not been deployed
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.
Updated strings from microsoft/vscode-loc-drop@0d6c79fe1758ae1e79bf289e187c477e0bc439ec