Repository navigation
Releases
Releases · jlusky/vscode-ha-config
v3.0.1
v3.0.0
HA Config - Home Assistant Configuration
This is the first release of blown.vscode-ha-config, a maintained fork of keesschollaart81/vscode-home-assistant (last released as 2.2.0). It brings the dependencies up to date, upgrades the YAML engine and ships a much smaller extension.
⚠️ Before you upgrade
- New extension ID. This is a separate Marketplace listing:
blown.vscode-ha-config. It does not update the original extension. Uninstall or disablekeesschollaart.vscode-home-assistantfirst; with both enabled you'd get duplicate diagnostics and completions. - Settings and commands are renamed from
vscode-home-assistant.*tovscode-ha-config.*. Settings from the original extension aren't read, so move them over in yoursettings.json:vscode-home-assistant.hostUrl→vscode-ha-config.hostUrlvscode-home-assistant.longLivedAccessToken→vscode-ha-config.longLivedAccessToken- The same goes for
ignoreCertificates,disableAutomaticFileAssociationandautoRenderTemplates. - The
HASS_SERVER,HASS_TOKENandSUPERVISOR_TOKENenvironment variables work as before. - Keybindings that call
vscode-home-assistant.*commands need the new prefix too.
- Requires VS Code 1.101 or later (previously 1.99).
✨ Improvements
- yaml-language-server 2.0 (from 1.19), the engine behind YAML validation, completion and hover, with the upstream schema-validation fixes since 1.19.
- Language Server Protocol 3.18:
vscode-languageclientandvscode-languageserver9 → 11. - Smaller, faster-loading extension. The extension and its language server are bundled with esbuild: the package goes from 2,369 files (13.9 MB) to 67 files (3.6 MB), and VS Code loads two files at startup instead of walking
node_modules. - Updated Home Assistant client (
home-assistant-js-websocket9.8.1), plus currentaxiosandws.
🐛 Fixes
- Jinja editor settings now load. The Jinja language configuration (bracket matching, auto-closing, comment toggling) pointed at a file that didn't exist, so it never loaded.
- Safer logging: message types received from the Home Assistant server are no longer used as a
console.logformat string (CodeQLjs/tainted-format-string). - Completion matching: fixed a property-name regular expression in auto-completion (CodeQL
js/useless-regexp-character-escape).
🔒 Security
- All Dependabot and CodeQL alerts are resolved, and
npm auditreports 0 vulnerabilities.
🧰 Maintenance
These changes don't affect how the extension behaves.
- Builds on Node 24 and TypeScript 7, with ESLint 10 and no warnings allowed.
- CI runs the tests on Linux and macOS, and the schema-validation tests now check the diagnostics the language server actually reports.
- Releases publish from GitHub releases through Marketplace Trusted Publishing, with no stored tokens, and the
.vsixis attached to each release. - GitHub Actions are pinned to commit SHAs, and there are issue forms for bug reports and feature requests.
- A
vscode-ha-config.devMockConnectionsetting, for development only, serves a mock Home Assistant connection so schemas can be tested without a live instance.
Full list of changes: https://github.com/jlusky/vscode-ha-config/pulls?q=is%3Apr+is%3Amerged