chore(deps): bump the all group with 5 updates

[dependabot]

Bumps the all group with 5 updates:

Package	From	To
@astrojs/mdx	4.1.0	4.2.0
@tailwindcss/vite	4.0.12	4.0.14
astro	5.4.2	5.5.2
tailwindcss	4.0.12	4.0.14
@iconify-json/simple-icons	1.2.27	1.2.28

Updates @astrojs/mdx from 4.1.0 to 4.2.0

Release notes

Sourced from @​astrojs/mdx's releases.

@​astrojs/mdx@​4.2.0

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

@​astrojs/mdx@​4.1.1

Patch Changes

... (truncated)

Changelog

Sourced from @​astrojs/mdx's changelog.

4.2.0

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

4.1.1

... (truncated)

Commits

• 4277225 [ci] release (#13397)
• cb886dc Add experimental.headingIdCompat flag (#13352)
• a3327ff feat(markdown): add excludeLangs configuration to syntax highlighting (#13311)
• 725bc0d fix(deps): update all non-major dependencies (#13387)
• 10fae31 [ci] release (#13361)
• 16d6d41 fix(deps): update all non-major dependencies (#13346)
• See full diff in compare view

Updates @tailwindcss/vite from 4.0.12 to 4.0.14

Release notes

Sourced from @​tailwindcss/vite's releases.

v4.0.14

Fixed

• Do not extract candidates with JS string interpolation ${ (#17142)
• Fix extraction of variants containing . character (#17153)
• Fix extracting candidates in Clojure/ClojureScript (#17087)

v4.0.13

Fixed

• Fix Haml pre-processing (#17051)
• Ensure .node and .wasm files are not scanned for utilities (#17123)
• Improve performance when scanning JSON files (#17125)
• Fix extracting candidates containing dots in Haml, Pug, and Slim pre processors (#17094, #17085, #17113)
• Don't create invalid CSS when encountering a link wrapped in square brackets (#17129)

Changelog

Sourced from @​tailwindcss/vite's changelog.

[4.0.14] - 2025-03-13

Fixed

• Do not extract candidates with JS string interpolation ${ (#17142)
• Fix extraction of variants containing . character (#17153)
• Fix extracting candidates in Clojure/ClojureScript (#17087)

[4.0.13] - 2025-03-11

Fixed

• Fix Haml pre-processing (#17051)
• Ensure .node and .wasm files are not scanned for utilities (#17123)
• Improve performance when scanning JSON files (#17125)
• Fix extracting candidates containing dots in Haml, Pug, and Slim pre processors (#17094, #17085, #17113)
• Don't create invalid CSS when encountering a link wrapped in square brackets (#17129)

Commits

• 3c5903c Prepare v4.0.14 release (#17173)
• 4455048 Prepare release 4.0.13 (#17132)
• See full diff in compare view

Updates astro from 5.4.2 to 5.5.2

Release notes

Sourced from astro's releases.

astro@5.5.2

Patch Changes

• #13415 be866a1 Thanks @​ascorbic! - Reuses experimental session storage object between requests. This prevents memory leaks and improves performance for drivers that open persistent connections to a database.

• #13420 2f039b9 Thanks @​ematipico! - It fixes an issue that caused some regressions in how styles are bundled.

astro@5.5.1

Patch Changes

• #13413 65903c9 Thanks @​ascorbic! - Makes experimental flag optional

astro@5.5.0

Minor Changes

• #13402 3e7b498 Thanks @​ematipico! - Adds a new experimental flag called experimental.preserveScriptOrder that renders <script> and <style> tags in the same order as they are defined.

  When rendering multiple <style> and <script> tags on the same page, Astro currently reverses their order in your generated HTML output. This can give unexpected results, for example CSS styles being overridden by earlier defined style tags when your site is built.

  With the new preserveScriptOrder flag enabled, Astro will generate the styles in the order they are defined:

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

  For example, the following component has two <style> tags, and both define the same style for the body tag:

  <p>I am a component</p>
  <style>
    body {
      background: red;
    }
  </style>
  <style>
    body {
      background: yellow;
    }
  </style>

  Once the project is compiled, Astro will create an inline style where yellow appears first, and then red. Ultimately, the red background is applied:

... (truncated)

Changelog

Sourced from astro's changelog.

5.5.2

Patch Changes

• #13415 be866a1 Thanks @​ascorbic! - Reuses experimental session storage object between requests. This prevents memory leaks and improves performance for drivers that open persistent connections to a database.

• #13420 2f039b9 Thanks @​ematipico! - It fixes an issue that caused some regressions in how styles are bundled.

5.5.1

Patch Changes

• #13413 65903c9 Thanks @​ascorbic! - Makes experimental flag optional

5.5.0

Minor Changes

• #13402 3e7b498 Thanks @​ematipico! - Adds a new experimental flag called experimental.preserveScriptOrder that renders <script> and <style> tags in the same order as they are defined.

  When rendering multiple <style> and <script> tags on the same page, Astro currently reverses their order in your generated HTML output. This can give unexpected results, for example CSS styles being overridden by earlier defined style tags when your site is built.

  With the new preserveScriptOrder flag enabled, Astro will generate the styles in the order they are defined:

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

  For example, the following component has two <style> tags, and both define the same style for the body tag:

  <p>I am a component</p>
  <style>
    body {
      background: red;
    }
  </style>
  <style>
    body {
      background: yellow;
    }
  </style>

... (truncated)

Commits

• 61b7154 [ci] release (#13418)
• 2f039b9 Revert "Replace internal cssScopeTo implementation to vite.cssScopeTo" (#13420)
• be866a1 fix: reuse storage objects in sessions (#13415)
• 118d3e1 [ci] release (#13414)
• 65903c9 fix: make preserveScriptOrder an optional flag (#13413)
• 4277225 [ci] release (#13397)
• 3b5196d [ci] format
• fd70537 chore: breakdown changelog (#13410)
• fb6859a docs: fix formatting of excludeLangs default value (#13408)
• 0efdc22 fix: rethrow astroerrors in image processing (#13407)
• Additional commits viewable in compare view

Updates tailwindcss from 4.0.12 to 4.0.14

Release notes

Sourced from tailwindcss's releases.

v4.0.14

Fixed

• Do not extract candidates with JS string interpolation ${ (#17142)
• Fix extraction of variants containing . character (#17153)
• Fix extracting candidates in Clojure/ClojureScript (#17087)

v4.0.13

Fixed

• Fix Haml pre-processing (#17051)
• Ensure .node and .wasm files are not scanned for utilities (#17123)
• Improve performance when scanning JSON files (#17125)
• Fix extracting candidates containing dots in Haml, Pug, and Slim pre processors (#17094, #17085, #17113)
• Don't create invalid CSS when encountering a link wrapped in square brackets (#17129)

Changelog

Sourced from tailwindcss's changelog.

[4.0.14] - 2025-03-13

Fixed

• Do not extract candidates with JS string interpolation ${ (#17142)
• Fix extraction of variants containing . character (#17153)
• Fix extracting candidates in Clojure/ClojureScript (#17087)

[4.0.13] - 2025-03-11

Fixed

• Fix Haml pre-processing (#17051)
• Ensure .node and .wasm files are not scanned for utilities (#17123)
• Improve performance when scanning JSON files (#17125)
• Fix extracting candidates containing dots in Haml, Pug, and Slim pre processors (#17094, #17085, #17113)
• Don't create invalid CSS when encountering a link wrapped in square brackets (#17129)

Commits

• 3c5903c Prepare v4.0.14 release (#17173)
• 215f4f3 Add @source inline(…) (#17147)
• 4455048 Prepare release 4.0.13 (#17132)
• See full diff in compare view

Updates @iconify-json/simple-icons from 1.2.27 to 1.2.28

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions