All notable changes to the SFMC DevTools VS Code extension are documented in GitHub Releases.
Publishing is triggered automatically via GitHub Actions when a new release is created.
- Bundled extension pack: the extension no longer auto-installs ESLint, EditorConfig, Prettier, SFMC Language Service, and SFMC Data Loader. It is now a standalone extension.
- README: added a "Recommended companion extensions" section pointing to the SFMC Extension Pack and SFMC Extension Pack Plus, and strongly recommending at least the SFMC Language Service extension.
- Cursor compatibility: lowered the required
engines.vscodefrom^1.109.0back to^1.101.0so the extension installs in Cursor (whose bundled VS Code base lags upstream). The1.109floor made the extension uninstallable in Cursor with an "is not compatible" error.
- Build (Template + Definition): the two Business Unit quick-picks now say source vs target so it is clear which selection maps to
--buFromand which to--buTo.
- Build (Template + Definition): the command now asks whether to clear the deploy folder before building and passes
--purgeor--no-purgeto mcdev so the CLI no longer waits indefinitely on an interactive prompt in the VS Code terminal.
- What's New: after an update, a notification offers to open in-editor release notes (parsed from this changelog). Command: SFMC DevTools: Show What's New. Full histories remain on GitHub Releases.
- Release notes: use SFMC DevTools: Show What's New in the Command Palette, or respond to the notification after an update, to open in-editor notes parsed from this changelog. For full details, see GitHub Releases.