Bump astro and @astrojs/mdx

[dependabot]

Bumps astro and @astrojs/mdx. These dependencies needed to be updated together.
Updates astro from 4.16.18 to 5.1.1

Release notes

Sourced from astro's releases.

[email protected]

Patch Changes

• #12782 f3d8385 Thanks @​fhiromasa! - update comment in packages/astro/src/types/public/common.ts

• #12789 f632b94 Thanks @​ascorbic! - Pass raw frontmatter to remark plugins in glob loader

• #12799 739dbfb Thanks @​ascorbic! - Upgrades Vite to pin esbuild

[email protected]

Minor Changes

• #12441 b4fec3c Thanks @​ascorbic! - Adds experimental session support

  Sessions are used to store user state between requests for server-rendered pages, such as login status, shopping cart contents, or other user-specific data.

  ---
  export const prerender = false; // Not needed in 'server' mode
  const cart = await Astro.session.get('cart');
  ---
  <a href="/checkout">🛒 {cart?.length ?? 0} items</a>

  Sessions are available in on-demand rendered/SSR pages, API endpoints, actions and middleware. To enable session support, you must configure a storage driver.

  If you are using the Node.js adapter, you can use the fs driver to store session data on the filesystem:

  // astro.config.mjs
  {
    adapter: node({ mode: 'standalone' }),
    experimental: {
      session: {
        // Required: the name of the unstorage driver
        driver: "fs",
      },
    },
  }

  If you are deploying to a serverless environment, you can use drivers such as redis, netlify-blobs, vercel-kv, or cloudflare-kv-binding and optionally pass additional configuration options.

  For more information, including using the session API with other adapters and a full list of supported drivers, see the docs for experimental session support. For even more details, and to leave feedback and participate in the development of this feature, the Sessions RFC.

• #12426 3dc02c5 Thanks @​oliverlynch! - Improves asset caching of remote images

  Astro will now store entity tags and the Last-Modified date for cached remote images and use them to revalidate the cache when it goes stale.

... (truncated)

Changelog

Sourced from astro's changelog.

5.1.1

Patch Changes

• #12782 f3d8385 Thanks @​fhiromasa! - update comment in packages/astro/src/types/public/common.ts

• #12789 f632b94 Thanks @​ascorbic! - Pass raw frontmatter to remark plugins in glob loader

• #12799 739dbfb Thanks @​ascorbic! - Upgrades Vite to pin esbuild

5.1.0

Minor Changes

• #12441 b4fec3c Thanks @​ascorbic! - Adds experimental session support

  Sessions are used to store user state between requests for server-rendered pages, such as login status, shopping cart contents, or other user-specific data.

  ---
  export const prerender = false; // Not needed in 'server' mode
  const cart = await Astro.session.get('cart');
  ---
  <a href="/checkout">🛒 {cart?.length ?? 0} items</a>

  Sessions are available in on-demand rendered/SSR pages, API endpoints, actions and middleware. To enable session support, you must configure a storage driver.

  If you are using the Node.js adapter, you can use the fs driver to store session data on the filesystem:

  // astro.config.mjs
  {
    adapter: node({ mode: 'standalone' }),
    experimental: {
      session: {
        // Required: the name of the unstorage driver
        driver: "fs",
      },
    },
  }

  If you are deploying to a serverless environment, you can use drivers such as redis, netlify-blobs, vercel-kv, or cloudflare-kv-binding and optionally pass additional configuration options.

  For more information, including using the session API with other adapters and a full list of supported drivers, see the docs for experimental session support. For even more details, and to leave feedback and participate in the development of this feature, the Sessions RFC.

• #12426 3dc02c5 Thanks @​oliverlynch! - Improves asset caching of remote images

... (truncated)

Commits

• 5f4c543 [ci] release (#12790)
• 739dbfb fix(deps): upgrade Vite (#12799)
• f3d8385 update comment in packages/astro/src/types/public/common.ts (#12782)
• 49cc5d7 [ci] format
• f632b94 fix: pass raw frontmatter to when parsing markdown in glob loader (#12789)
• 5e9d1bc chore: move files to .mjs (#12765)
• 73b6c8b chore: fix links in session errors (#12787)
• 3f557b2 [ci] release (#12762)
• 4353fc5 fix: correctly return 404.astro in i18n (#12764)
• 45005a5 [ci] format
• Additional commits viewable in compare view

Updates @astrojs/mdx from 3.1.9 to 4.0.3

Release notes

Sourced from @​astrojs/mdx's releases.

@​astrojs/mdx@​4.0.3

Patch Changes

• #12799 739dbfb Thanks @​ascorbic! - Upgrades Vite to pin esbuild

@​astrojs/mdx@​4.0.2

Patch Changes

• Updated dependencies [f13417b, 87231b1, a71e9b9]:
  • @​astrojs/markdown-remark@​6.0.1

@​astrojs/mdx@​4.0.1

Patch Changes

• #12594 4f2fd0a Thanks @​Princesseuh! - Fixes compatibility with Astro 5

@​astrojs/mdx@​4.0.0

Major Changes

• #12231 90ae100 Thanks @​bluwy! - Handles the breaking change in Astro where content pages (including .mdx pages located within src/pages/) no longer respond with charset=utf-8 in the Content-Type header.

  For MDX pages without layouts, @astrojs/mdx will automatically add the <meta charset="utf-8"> tag to the page by default. This reduces the boilerplate needed to write with non-ASCII characters. If your MDX pages have a layout, the layout component should include the <meta charset="utf-8"> tag.

  If you require charset=utf-8 to render your page correctly, make sure that your layout components have the <meta charset="utf-8"> tag added.

• #12008 5608338 Thanks @​Princesseuh! - Welcome to the Astro 5 beta! This release has no changes from the latest alpha of this package, but it does bring us one step closer to the final, stable release.

  Starting from this release, no breaking changes will be introduced unless absolutely necessary.

  To learn how to upgrade, check out the Astro v5.0 upgrade guide in our beta docs site.

Minor Changes

• #12539 827093e Thanks @​bluwy! - Drops node 21 support

• #11741 6617491 Thanks @​bluwy! - Updates adapter server entrypoint to use @astrojs/mdx/server.js

  This is an internal change. Handling JSX in your .mdx files has been moved from Astro internals and is now the responsibility of this integration. You should not notice a change in your project, and no update to your code is required.

Patch Changes

• #12075 a19530e Thanks @​bluwy! - Parses frontmatter ourselves

• #11861 3ab3b4e Thanks @​bluwy! - Updates @astrojs/markdown-remark and handle its breaking changes

• #12533 1b61fdf Thanks @​ematipico! - Fixes a case where the MDX renderer couldn't be loaded when used as a direct dependency of an Astro integration.

• Updated dependencies [3ab3b4e, 5608338, 560ef15, 83a2a64, 3ab3b4e, a19530e]:

  • @​astrojs/markdown-remark@​6.0.0

... (truncated)

Changelog

Sourced from @​astrojs/mdx's changelog.

4.0.3

Patch Changes

• #12799 739dbfb Thanks @​ascorbic! - Upgrades Vite to pin esbuild

4.0.2

Patch Changes

• Updated dependencies [f13417b, 87231b1, a71e9b9]:
  • @​astrojs/markdown-remark@​6.0.1

4.0.1

Patch Changes

• #12594 4f2fd0a Thanks @​Princesseuh! - Fixes compatibility with Astro 5

4.0.0

Major Changes

• #12231 90ae100 Thanks @​bluwy! - Handles the breaking change in Astro where content pages (including .mdx pages located within src/pages/) no longer respond with charset=utf-8 in the Content-Type header.

  For MDX pages without layouts, @astrojs/mdx will automatically add the <meta charset="utf-8"> tag to the page by default. This reduces the boilerplate needed to write with non-ASCII characters. If your MDX pages have a layout, the layout component should include the <meta charset="utf-8"> tag.

  If you require charset=utf-8 to render your page correctly, make sure that your layout components have the <meta charset="utf-8"> tag added.

• #12008 5608338 Thanks @​Princesseuh! - Welcome to the Astro 5 beta! This release has no changes from the latest alpha of this package, but it does bring us one step closer to the final, stable release.

  Starting from this release, no breaking changes will be introduced unless absolutely necessary.

  To learn how to upgrade, check out the Astro v5.0 upgrade guide in our beta docs site.

Minor Changes

• #12539 827093e Thanks @​bluwy! - Drops node 21 support

• #11741 6617491 Thanks @​bluwy! - Updates adapter server entrypoint to use @astrojs/mdx/server.js

  This is an internal change. Handling JSX in your .mdx files has been moved from Astro internals and is now the responsibility of this integration. You should not notice a change in your project, and no update to your code is required.

Patch Changes

• #12075 a19530e Thanks @​bluwy! - Parses frontmatter ourselves

• #11861 3ab3b4e Thanks @​bluwy! - Updates @astrojs/markdown-remark and handle its breaking changes

• #12533 1b61fdf Thanks @​ematipico! - Fixes a case where the MDX renderer couldn't be loaded when used as a direct dependency of an Astro integration.

... (truncated)

Commits

• 5f4c543 [ci] release (#12790)
• 739dbfb fix(deps): upgrade Vite (#12799)
• 163cfd6 [ci] release (#12650)
• 7a02982 [ci] release (#12595)
• 4f2fd0a fix: cleanup peer deps ranges (#12594)
• fcdd37f [ci] release (#12567)
• 218267c [ci] release (beta) (#12534)
• 2da81e5 Merge branch 'main' into next
• 827093e Drop node 21 support (#12539)
• 9f44019 Update Vite to 6.0.0 (#12524)
• Additional commits viewable 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)