Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@pmndrs/docs@3.5.0

Minor Changes

• #562 8415ecf Thanks @abernier! - Serve the pmndrs example gallery over MCP, next to the docs: an examples://index resource listing every published demo with its description, libraries and tags, and a get_example tool returning one demo in full -- source files, the dependency versions it is written against, and asset attribution. Reads the JSON catalog pmndrs/examples publishes at /catalog/; override the origin with EXAMPLES_URL to develop against a local build.

Patch Changes

• #565 3272ad5 Thanks @abernier! - Follow the examples gallery to guessable URLs: an example's document is now its page URL with .md on the end (/examples/caustics.md), and the gallery index is /llms.txt — the same root convention every site built with this generator already publishes. index no longer needs reserving as a name, since it no longer collides with anything.

• #564 2318b88 Thanks @abernier! - Pass the example gallery through as published rather than rendering it here. pmndrs/examples now writes the documents at build time and links each one from its page with rel="alternate", so examples://index and get_example hand on the same text an agent would get from the open web — one rendering instead of two that could drift. The agents page documents both tools.

• #572 96c442f Thanks @abernier! - globals.css stops restating the colour layer by hand. The ~60-line @theme mapping is now @plugin 'material-theme-builder/tailwind', which declares the same names and takes the five alert colours as an option; the 31-line shadcn remap is now @import 'material-theme-builder/shadcn.css', which is where those exact 31 declarations came from. 95 lines removed, nothing to keep in sync.

• #572 96c442f Thanks @abernier! - Move the colour engine from react-mcu to material-theme-builder, its successor. At the API level it is a rename: --mcu-* becomes --md-sys-color-*, the standard MD3 system-token name. The --color-* names the @theme mapping declares are unchanged, so every bg-surface, bg-primary-container and text-on-surface-variant keeps working untouched, and the THEME_* env vars behave exactly as before.

  The palette is not quite identical, though. 57 of the 67 roles match exactly, including all 49 standard M3 ones; the 10 that differ all belong to the five blend: true custom colours, which the two packages harmonize differently. In practice the markdown alerts get more muted backgrounds — most visibly Important and Caution, whose hues sit furthest from the seed. Tip and Warning are unchanged.

  Two components name the raw variables rather than a Tailwind utility — Code for its fixed prism colour, Sandpack for its three surface levels — and are the only component edits.