What's New
This release fixes the broken update function. Now the update ability works without fail (hopefully).
Bug Fixes
- Fixed reversed ExecToStack pop order — nsExec::ExecToStack pushes stdout first and the exit code on top; the previous code popped them in the wrong order, meaning version checks and download error handling were reading the wrong values from the stack.
- Fixed register collision between GetDllVersion and CompareVersions — both operations were sharing $R0, causing the version comparison result to silently clobber DLL version data. The comparison now uses a dedicated scratch register.
- Fixed false "already up to date" on builds with a non-zero build field — the local version was being compared as X.Y.Z.build against the API's X.Y.Z, causing VS Code to appear newer than it was and suppressing valid updates. The build field is now normalized to 0 before comparison.
- Fixed empty version guard that was always false — the RemoteVersion empty-string check ran after .0 had already been appended, so the string could never be empty and bad API responses would silently proceed. The check now runs against the raw parsed value before any modification.
- Fixed 7za.exe path failing in cmd subprocesses — the extractor was referenced by a bare filename, which is not on cmd's search path when launched via nsExec. Both 7za.exe and curl.exe/jq.exe are now staged to $PLUGINSDIR and referenced by their full absolute paths.
- Fixed backup directory leaking on successful update — the ${APPDIR}-backup folder was left on disk after a successful extraction. It is now removed once the update is verified complete.
- Fixed missing Goto _FINISHED at end of _FAILED block — the failure handler had no explicit jump, making the code fragile against future edits that add anything between _FAILED and _FINISHED.
Note
If an extraction failure occurs, the launcher automatically restores the backed-up installation before surfacing the error message.
Full Changelog: 1.103.2...1.131.0