VS Code 1.145.2 patches restricted event handling in open-source editor
Microsoft's VS Code 1.145.2 release tightens event validation by dropping unrecognized restricted events, a targeted security-hardening fix in the MIT-licensed editor.
Summary
Microsoft has published VS Code 1.145.2, a patch-level update to its widely used open-source code editor. The release addresses event handling behavior by dropping unrecognized restricted events, a change merged via pull request #346 into the 1.145 branch. VS Code remains available under the MIT license, with its source code developed in the open on GitHub and built on the Electron framework. The update carries a verified GitHub signature from maintainer amunger and was tagged on November 6, 2026.
This is a maintenance release rather than a feature update, focused on hardening the editor's internal event system. VS Code serves as the foundation for numerous downstream distributions including VSCodium and various Linux distribution packages, making even incremental patches relevant to the broader open-source development tooling ecosystem.
What changes in VS Code 1.145.2
- Event validation: The release drops unrecognized restricted events, preventing potentially malformed or unauthorized event objects from propagating through the editor's internal event bus.
- Version bump: The change increments the patch version from the 1.145 base to 1.145.2, indicating a targeted fix rather than minor or major feature work.
- Merge context: The fix was integrated through pull request #346, suggesting peer-reviewed code review before inclusion in the stable branch.
- Supply chain integrity: The release tag is cryptographically verified with GitHub's signature using GPG key ID B5690EEEBB952194, signed by Microsoft maintainer amunger.
Why it matters
For Linux distribution packagers and VSCodium maintainers who strip Microsoft's proprietary telemetry and branding, this patch provides a clean upstream fix to cherry-pick without additional event-handling patches of their own. The change also matters for extension developers who rely on VS Code's restricted event API, as the stricter validation may surface previously tolerated edge cases in extension code.
Original reference: github.com →