v2.2.0

What's Changed

• Maintenance guards: version/protocol drift, typecheck in CI, deps and Actions by @Guiqft in #5
• Maintenance cleanup: Prettier, docs-drift guard, drop inherited assets by @Guiqft in #7
• build(deps-dev): bump typescript from 5.9.3 to 7.0.2 by @dependabot[bot] in #6
• feat: flag decks running an outdated plugin by @Guiqft in #8

New Contributors

• @dependabot[bot] made their first contribution in #6

Full Changelog: v2.1.0...v2.2.0

v2.1.0

Pre-2.0 plugins work again

2.0.0 replaced the ad-hoc bridge with a broker and a versioned hello. Anything that did not send that hello was parked as "unidentified" — which is exactly what a 1.x plugin does. Every deck installed before 2.0 went dark the moment npx resolved the new server, and the plugin window in Figma kept saying "Connected".

The broker now probes a socket that stays silent past the identify window. Any answer identifies it as a plugin, and the answer carries the file name, so a legacy deck registers under its real name and routes commands normally.

• list_decks marks those decks legacy: true
• ping and use_deck return the update steps alongside the result
• the "no deck connected" error now carries the download URL and the three update steps, and only fires for sockets that answer nothing at all

The plugin bundle is unchanged — the figma-plugin.zip attached here is byte-identical to the one in 2.0.1. Updating the plugin is still worth doing: the 1.x build reconnects from a timer Figma throttles in hidden iframes, so it can stay dark after the broker restarts.

Full Changelog: v2.0.1...v2.1.0

v2.0.1

Important

Breaking change for anyone who installed the Figma plugin before 2.0.0.

2.0.0 moved the WebSocket bridge into a broker daemon with a versioned handshake. A 1.x plugin connects but never registers, so every tool answers "No Figma deck is connected" — while the plugin window in Figma still says "Connected to MCP server".

Fix: download figma-plugin.zip below, unzip it over the folder you imported into Figma, and re-run the plugin (Plugins > Development > Claude Code Slides). manifest.json has not changed since 1.x, so you only need to re-import if that folder moved.

Server 2.1.0 and later serve a pre-2.0 plugin through a compatibility path, so updating the server clears this too.

What's Changed

• fix: name the outdated plugin instead of reporting an empty bridge by @Guiqft in #4

Full Changelog: v2.0.0...v2.0.1

v2.0.0

Important

Breaking change for anyone who installed the Figma plugin before 2.0.0.

2.0.0 moved the WebSocket bridge into a broker daemon with a versioned handshake. A 1.x plugin connects but never registers, so every tool answers "No Figma deck is connected" — while the plugin window in Figma still says "Connected to MCP server".

Fix: download figma-plugin.zip below, unzip it over the folder you imported into Figma, and re-run the plugin (Plugins > Development > Claude Code Slides). manifest.json has not changed since 1.x, so you only need to re-import if that folder moved.

Server 2.1.0 and later serve a pre-2.0 plugin through a compatibility path, so updating the server clears this too.

What's Changed

• feat!: persistent broker daemon and multi-deck routing by @Guiqft in #3

Full Changelog: v1.2.0...v2.0.0

v1.2.0

Full Changelog: v1.1.0...v1.2.0

v1.1.0

Full Changelog: v1.0.2...v1.1.0

v1.0.2

Full Changelog: v1.0.1...v1.0.2

v1.0.1

Full Changelog: v1.0.0...v1.0.1