Repository navigation
Releases
v0.22.19
LeetCode Live Share v0.22.19
This release ensures a previous session's unpushed work is never hidden behind a fresh Codespace.
- If the host reruns the launcher while GitHub is still stopping an idle Codespace (
ShuttingDown), the extension now waits for it and starts the same Codespace. The old reuse allow-list skipped that state and created an empty Codespace frommain, making unpushed solutions and notes look lost (they were recoverable from the original Codespace and its backup branch). - The most recently used Codespace is reused in every state except
Deleted. A new Codespace is created only when none remains. Failed,Unavailable, andArchivedCodespaces produce an actionable error instead of being silently replaced. Codespaces withoutlast_used_atare no longer dropped from selection.- Patch-level updates clear newly published high-severity npm advisories (
axios1.20.0,follow-redirects1.16.2,markdown-it14.3.3,sanitize-html2.18.1,source-map-js1.2.2,undici6.29.1,js-yaml3.15.2,brace-expansion1.1.21,minimatch3.1.5,moment2.31.0,qs6.16.1). Only the legacy CLI's unfixable moderaterequest/uuid@3findings remain. - The launcher scripts are unchanged from v0.22.18; the ZIP carries the new lock.
Verified source commits:
- Extension tag target:
62449cd1cd8c47a7c8e4bf845f31ff64f9f4d8a9(PR #22; Windows/Linux CI passed on the branch and onmaster) - Launcher/lock source candidate:
d1f0c28(ChaosLights/lcPR LeetCode-OpenSource#39)
Artifact checksums:
153398d6754fd56edc5c6841251ebc17d154bf814f516e2cb746c29033174711 vscode-leetcode-live-share-0.22.19.vsix
60994edc184ea4159ab59e9d439cd89e31882b640da5a3da247c2a4f87628956 leetcode-pairing-launcher-v0.22.19.zip
Both assets and the annotated tag are immutable. Any future correction will use a new patch version rather than replacing these files.
v0.22.18
LeetCode Live Share v0.22.18
This release hardens judge-session recovery and makes the release artifacts immutable.
- Coalesces concurrent CLI session rebuilds globally, including Test, Submit, and problem-list recovery on different files.
- Distinguishes Cloudflare managed challenges without claiming that the login is valid or that source code was necessarily the trigger.
- Shows the known Python division rewrite hint only when a
.pysolution actually contains the reproducedint(float(...)/...)form. - Migrates the bundled CLI to the neutral Cloudflare classifier v2 while retaining compatibility with v0.22.16/17 error text.
- Pins patched transitive versions of
js-yaml,nanoid,postcss, andundici; no high or critical npm audit findings remain. - Includes the launcher fix that invokes Stable
Code.exedirectly, so URI query fields such as&issue=8cannot be split into shell commands bycode.cmd.
Verified source commits:
- Extension tag target:
30bec5ef436a16999b0aa58a61bd8a7e30b59731 - Launcher/lock source candidate:
e39992c(ChaosLights/lcPR LeetCode-OpenSource#37)
Artifact checksums:
ab3e7b9717688369d1e13da0294b18258251f7abe467ad1cf9644818d6bc273b vscode-leetcode-live-share-0.22.18.vsix
59990278384e56cc9d5e9b83d0c7a35435d15eadf33cc67dd1645f9d24e537d3 leetcode-pairing-launcher-v0.22.18.zip
Both assets and the annotated tag are immutable. Any future correction will use a new patch version rather than replacing these files.
v0.22.17
Fixes a stale per-file judge lock: Test and Submit now become available immediately after the CLI operation and temporary-file cleanup finish, even while an error notification remains open.
This retains the v0.22.16 Cloudflare challenge diagnosis and session recovery behavior.
Launcher hotfix (2026-08-16): the Windows launcher now invokes Stable Code.exe directly for the pairing URI. This prevents code.cmd/cmd.exe from treating URI ampersands as shell command separators and reporting that 'issue' is not a command.
v0.22.16
Correctly distinguish Cloudflare managed challenges from expired LeetCode sessions.
The bundled legacy CLI previously converted every HTTP 401/403 into session expired. A real Python 150 Test showed that int(float(a)/b) triggered a Cloudflare HTML challenge while the same authenticated request using the equivalent int(a * 1.0 / b) was accepted and returned 9.
This release inspects the response server, content type, and challenge page before classifying the error; genuine session recovery remains unchanged. It also gives an actionable rewrite hint and reproducibly patches/verifies the bundled CLI during clean builds.
Validated by clean npm install, unit/process tests, Windows and Linux VS Code integration tests, VSIX packaging, and real LeetCode judge requests.
v0.22.15
Fix transient LeetCode judge session rejection immediately after login.
- Test and Submit recover from the explicit session-expired response with bounded backoff.
- The isolated CLI session is rebuilt once from the already verified cookie; repeated browser login is not required.
- Submit is retried only before the judge accepts the initial POST, preventing duplicate submissions.
- Other judge, compiler, timeout, and cancellation errors remain single-attempt failures.
Validated on Windows and Linux CI, VS Code integration tests, VSIX packaging, and a real LeetCode judge request.
v0.22.14
Eliminates the recurring Windows terminal flashes during LeetCode Pairing by replacing 15–20 second GitHub CLI subprocesses with authenticated GitHub REST requests. Reuses VS Code GitHub authentication, keeps an encrypted one-time CLI fallback, removes duplicate host polling, and preserves automatic Codespace lifecycle handling.
v0.22.13
Remove the Excalidraw companion from the pairing flow.
- Excalidraw is a web-only extension; an earlier release pinned it to
remote.extensionKind: ["ui"]in global settings, which excludes the web worker host it needs and prevented it from running at all (blank editor,command 'excalidraw.*' not found). It is now removed from the extension pack, the reproducible companion VSIX packaging is deleted, and it is no longer pinned in the launcher lock. ensureLocalExtensionKindsnow removes any stalepomdtr.excalidraw-editoroverride from the globalremote.extensionKindsetting so affected machines self-heal.- Shared drawings should use excalidraw.com; the
.excalidrawformat is compatible.
v0.22.12
Deep activation and remote-workspace hardening.\n\n- Ships an activation-fixed Excalidraw 3.9.301 companion built reproducibly from the audited official 3.9.3 Marketplace VSIX.\n- Explicitly declares every LeetCode command activation event.\n- Fixes invalid empty problem-tree decorations on VS Code 1.119.\n- Adds Excalidraw readiness diagnostics and regression coverage.\n\nThe Excalidraw companion retains pomdtr's MIT-licensed implementation; only its version and activation declarations are changed.
v0.22.11
Fix Excalidraw custom editor activation for Codespace and Live Share workspace files. The local LeetCode extension now explicitly activates Excalidraw 3.9.3 so its Open command and editor are registered even though workspaceContains cannot see remote files.
LeetCode Live Share v0.22.10
Fixes stale Live Share invitations after the host window closes or the extension reloads. Join is now considered successful only after Live Share reaches the Guest role; host leases renew every 20 seconds, expire after 75 seconds, and are released during awaited extension shutdown. Includes regression coverage for delayed join confirmation, inactive-session timeout, stale heartbeat detection, and shutdown release.