withastro/astro @astrojs/markdoc@1.0.0

on GitHub

Minor Changes

• #14494 727b0a2 Thanks @florian-lefebvre! - Updates Markdown heading ID generation - (v6 upgrade guidance)

• #15345 840fbf9 Thanks @matthewp! - Uses Astro's new emitClientAsset API for image emission in content collections

• #15097 be1b9bf Thanks @matthewp! - Updates internal image processing to be compatible with Astro 6. This change is internal-only and does not affect the public API.

  The integration now uses Astro's new emitImageMetadata() function instead of the removed emitESMImage() function for processing images referenced in Markdoc content during build time. This ensures continued compatibility with Astro's asset processing pipeline while maintaining the same behavior for users.

• #14427 e131261 Thanks @florian-lefebvre! - Increases minimum Node.js version to 22.12.0 - (v6 upgrade guidance)

• #14445 ecb0b98 Thanks @florian-lefebvre! - Astro v6.0 upgrades to Vite v7.0 as the development server and production bundler - (v6 upgrade guidance)

Patch Changes

• #15184 f47c071 Thanks @ematipico! - Fixes an issue where the package wasn't correctly published

• #15457 6e8da44 Thanks @AhmadYasser1! - Fixes custom attributes on Markdoc's built-in {% table %} tag causing "Invalid attribute" validation errors.

  In Markdoc, table exists as both a tag ({% table %}) and a node (the inner table structure). When users defined custom attributes on either nodes.table or tags.table, the attributes weren't synced to the counterpart, causing validation to fail on whichever side was missing the declaration.

  The fix automatically syncs custom attribute declarations between tags and nodes that share the same name, so users can define attributes on either side and have them work correctly.

• #15264 11efb05 Thanks @florian-lefebvre! - Lower the Node version requirement to allow running on Stackblitz until it supports v22

• #15335 75931c2 Thanks @matthewp! - Fixes an issue where spreading a built-in Markdoc node config (e.g., ...Markdoc.nodes.fence) and specifying a custom render component would not work because the built-in transform() function was overriding the custom component. Now, render wins over transform when both are specified.

• Updated dependencies [bbb5811, bbb5811, 4ebc1e3, cb99214, 80f0225, 727b0a2, 11efb05, 4e7f3e8, a164c77, 1fa4177, 7c55f80, cf6ea6b, e131261, 6f19ecc, f94d3c5, a18d727, 240c317, 745e632]:

  • @astrojs/markdown-remark@7.0.0
  • @astrojs/prism@4.0.0
  • @astrojs/internal-helpers@0.8.0