chore(deps): update dependency @astrojs/markdoc to ^0.15.0

[mend-for-github-com]

This PR contains the following updates:

Package	Type	Update	Change
@astrojs/markdoc (source)	dependencies	minor	^0.12.11 -> ^0.15.0

By merging this PR, the below vulnerabilities will be automatically resolved:

Severity	CVSS Score	Vulnerability
Medium	5.4	CVE-2025-65019

---

Release Notes

withastro/astro (@​astrojs/markdoc)

v0.15.9

Compare Source

Patch Changes

• Updated dependencies [9e9c528, 0f75f6b]:
  • @​astrojs/internal-helpers@​0.7.5
  • @​astrojs/markdown-remark@​6.3.9

v0.15.8

Compare Source

Patch Changes

• Updated dependencies [b8ca69b]:
  • @​astrojs/internal-helpers@​0.7.4
  • @​astrojs/markdown-remark@​6.3.8

v0.15.7

Compare Source

Patch Changes

• Updated dependencies [1e2499e]:
  • @​astrojs/internal-helpers@​0.7.3
  • @​astrojs/markdown-remark@​6.3.7

v0.15.6

Compare Source

Patch Changes

• #​14326 c24a8f4 Thanks @​jsparkdev! - Updates vite version to fix CVE

v0.15.5

Compare Source

Patch Changes

• Updated dependencies [4d16de7]:
  • @​astrojs/internal-helpers@​0.7.2
  • @​astrojs/markdown-remark@​6.3.6

v0.15.4

Compare Source

Patch Changes

• Updated dependencies [0567fb7]:
  • @​astrojs/internal-helpers@​0.7.1
  • @​astrojs/markdown-remark@​6.3.5

v0.15.3

Compare Source

Patch Changes

• Updated dependencies [f4e8889]:
  • @​astrojs/internal-helpers@​0.7.0
  • @​astrojs/markdown-remark@​6.3.4

v0.15.2

Compare Source

Patch Changes

• #​14147 211968c Thanks @​birtles! - Recognize a custom default image node component

v0.15.1

Compare Source

Patch Changes

• Updated dependencies [d8305f8]:
  • @​astrojs/markdown-remark@​6.3.10

v0.15.0

Compare Source

Minor Changes

• #​13809 3c3b492 Thanks @​ascorbic! - Increases minimum Node.js version to 18.20.8

  Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.

  ⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

Patch Changes

• Updated dependencies [3c3b492]:
  • @​astrojs/prism@​3.3.0
  • @​astrojs/markdown-remark@​6.3.2

v0.14.2

Compare Source

Patch Changes

• #​13731 c3e80c2 Thanks @​jsparkdev! - update vite to latest version for fixing CVE

v0.14.1

Compare Source

Patch Changes

• #​13591 5dd2d3f Thanks @​florian-lefebvre! - Removes unused code

v0.14.0

Compare Source

Minor Changes

• #​13578 406501a Thanks @​stramel! - The SVG import feature introduced behind a flag in v5.0.0 is no longer experimental and is available for general use.

  This feature allows you to import SVG files directly into your Astro project as components and inline them into your HTML.

  To use this feature, import an SVG file in your Astro project, passing any common SVG attributes to the imported component.

  ---
  import Logo from './path/to/svg/file.svg';
  ---
  
  <Logo <Logo width={64} height={64} fill="currentColor" />

  If you have been waiting for stabilization before using the SVG Components feature, you can now do so.

  If you were previously using this feature, please remove the experimental flag from your Astro config:

  import { defineConfig } from 'astro'
  
  export default defineConfig({
  -  experimental: {
  -    svg: true,
  -  }
  })

  Additionally, a few features that were available during the experimental stage were removed in a previous release. Please see the v5.6.0 changelog for details if you have not yet already updated your project code for the experimental feature accordingly.

  Please see the SVG Components guide in docs for more about this feature.

v0.13.4

Compare Source

Patch Changes

• #​13596 3752519 Thanks @​jsparkdev! - update vite to latest version to fix CVE

• #​13547 360cb91 Thanks @​jsparkdev! - Updates vite to the latest version

v0.13.3

Compare Source

Patch Changes

• #​13526 ff9d69e Thanks @​jsparkdev! - update vite to the latest version

v0.13.2

Patch Changes

• #​13505 a98ae5b Thanks @​ematipico! - Updates the dependency vite to the latest.

v0.13.1

Patch Changes

• Updated dependencies [91c9503]:
  • @​astrojs/markdown-remark@​6.3.1

v0.13.0

Compare Source

Minor Changes

• #​13352 cb886dc Thanks @​delucis! - Adds support for a new experimental.headingIdCompat flag

  By default, Astro removes a trailing - from the end of IDs it generates for headings ending with
  special characters. This differs from the behavior of common Markdown processors.

  You can now disable this behavior with a new configuration flag:

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  
  export default defineConfig({
    experimental: {
      headingIdCompat: true,
    },
  });

  This can be useful when heading IDs and anchor links need to behave consistently across your site
  and other platforms such as GitHub and npm.

  If you are using the rehypeHeadingIds plugin directly, you can also pass this new option:

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  import { rehypeHeadingIds } from '@​astrojs/markdown-remark';
  import { otherPluginThatReliesOnHeadingIDs } from 'some/plugin/source';
  
  export default defineConfig({
    markdown: {
      rehypePlugins: [
        [rehypeHeadingIds, { experimentalHeadingIdCompat: true }],
        otherPluginThatReliesOnHeadingIDs,
      ],
    },
  });

Patch Changes

• Updated dependencies [cb886dc, a3327ff]:
  • @​astrojs/markdown-remark@​6.3.0

---

• If you want to rebase/retry this PR, check this box

[mend-for-github-com]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: toolbar-app/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @astrojs/starlight-markdoc@0.2.0
npm error Found: @astrojs/markdoc@0.15.9
npm error node_modules/@astrojs/markdoc
npm error   @astrojs/markdoc@"^0.15.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @astrojs/markdoc@"^0.12.1" from @astrojs/starlight-markdoc@0.2.0
npm error node_modules/@astrojs/starlight-markdoc
npm error   @astrojs/starlight-markdoc@"^0.2.0" from the root project
npm error
npm error Conflicting peer dependency: @astrojs/markdoc@0.12.11
npm error node_modules/@astrojs/markdoc
npm error   peer @astrojs/markdoc@"^0.12.1" from @astrojs/starlight-markdoc@0.2.0
npm error   node_modules/@astrojs/starlight-markdoc
npm error     @astrojs/starlight-markdoc@"^0.2.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-12-05T15_15_43_577Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-12-05T15_15_43_577Z-debug-0.log