build(deps): bump the astro group with 3 updates

[dependabot]

Bumps the astro group with 3 updates: astro, @astrojs/mdx and @astrojs/sitemap.

Updates astro from 4.8.6 to 4.10.1

Release notes

Sourced from astro's releases.

[email protected]

Patch Changes

• #11198 8b9a499 Thanks @​florian-lefebvre! - Fixes a case where astro:env getSecret would not retrieve environment variables properly in dev and build modes

• #11206 734b98f Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental astro:env feature only

  Updates the adapter astro:env entrypoint from astro:env/setup to astro/env/setup

• #11205 8c45391 Thanks @​Nin3lee! - Fixes a typo in the config reference

[email protected]

Minor Changes

• #10974 2668ef9 Thanks @​florian-lefebvre! - Adds experimental support for the astro:env API.

  The astro:env API lets you configure a type-safe schema for your environment variables, and indicate whether they should be available on the server or the client. Import and use your defined variables from the appropriate /client or /server module:

  ---
  import { PUBLIC_APP_ID } from 'astro:env/client';
  import { PUBLIC_API_URL, getSecret } from 'astro:env/server';
  const API_TOKEN = getSecret('API_TOKEN');
  const data = await fetch(${PUBLIC_API_URL}/users, {
  method: 'POST',
  headers: {
  'Content-Type': 'application/json',
  Authorization: Bearer ${API_TOKEN},
  },
  body: JSON.stringify({ appId: PUBLIC_APP_ID }),
  });

  To define the data type and properties of your environment variables, declare a schema in your Astro config in experimental.env.schema. The envField helper allows you define your variable as a string, number, or boolean and pass properties in an object:

  // astro.config.mjs
  import { defineConfig, envField } from 'astro/config';
  export default defineConfig({
  experimental: {
  env: {
  schema: {
  PUBLIC_API_URL: envField.string({ context: 'client', access: 'public', optional: true }),
  PUBLIC_PORT: envField.number({ context: 'server', access: 'public', default: 4321 }),
  API_SECRET: envField.string({ context: 'server', access: 'secret' }),
  },
  },

... (truncated)

Changelog

Sourced from astro's changelog.

4.10.1

Patch Changes

• #11198 8b9a499 Thanks @​florian-lefebvre! - Fixes a case where astro:env getSecret would not retrieve environment variables properly in dev and build modes

• #11206 734b98f Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental astro:env feature only

  Updates the adapter astro:env entrypoint from astro:env/setup to astro/env/setup

• #11205 8c45391 Thanks @​Nin3lee! - Fixes a typo in the config reference

4.10.0

Minor Changes

• #10974 2668ef9 Thanks @​florian-lefebvre! - Adds experimental support for the astro:env API.

  The astro:env API lets you configure a type-safe schema for your environment variables, and indicate whether they should be available on the server or the client. Import and use your defined variables from the appropriate /client or /server module:

  ---
  import { PUBLIC_APP_ID } from 'astro:env/client';
  import { PUBLIC_API_URL, getSecret } from 'astro:env/server';
  const API_TOKEN = getSecret('API_TOKEN');
  const data = await fetch(${PUBLIC_API_URL}/users, {
  method: 'POST',
  headers: {
  'Content-Type': 'application/json',
  Authorization: Bearer ${API_TOKEN},
  },
  body: JSON.stringify({ appId: PUBLIC_APP_ID }),
  });

  To define the data type and properties of your environment variables, declare a schema in your Astro config in experimental.env.schema. The envField helper allows you define your variable as a string, number, or boolean and pass properties in an object:

  // astro.config.mjs
  import { defineConfig, envField } from 'astro/config';
  export default defineConfig({
  experimental: {
  env: {
  schema: {
  PUBLIC_API_URL: envField.string({ context: 'client', access: 'public', optional: true }),
  PUBLIC_PORT: envField.number({ context: 'server', access: 'public', default: 4321 }),
  API_SECRET: envField.string({ context: 'server', access: 'secret' }),

... (truncated)

Commits

• 2da877b [ci] release (#11201)
• 734b98f feat(astro): update astro env setup (#11206)
• 8c45391 fix(astro:) config reference typo (#11205)
• 368e4ce [ci] format
• 8b9a499 fix(astro): getSecret in dev and build (#11198)
• 48d5309 [ci] release (#11186)
• 97fbe93 fix: merge userConfig inside getViteConfig (#11194)
• a64428d [ci] format
• 6e29a17 Make Astro.url in format: 'preserve' match dev (#11191)
• 58b10a0 Fix throw AstroUserError in mdx (#11192)
• Additional commits viewable in compare view

Updates @astrojs/mdx from 3.0.0 to 3.1.0

Release notes

Sourced from @​astrojs/mdx's releases.

@​astrojs/mdx@​3.1.0

Minor Changes

• #11144 803dd80 Thanks @​ematipico! - The integration now exposes a function called getContainerRenderer, that can be used inside the Container APIs to load the relative renderer.

  import { experimental_AstroContainer as AstroContainer } from 'astro/container';
  import ReactWrapper from '../src/components/ReactWrapper.astro';
  import { loadRenderers } from 'astro:container';
  import { getContainerRenderer } from '@astrojs/react';
  test('ReactWrapper with react renderer', async () => {
  const renderers = await loadRenderers([getContainerRenderer()]);
  const container = await AstroContainer.create({
  renderers,
  });
  const result = await container.renderToString(ReactWrapper);
  expect(result).toContain('Counter');
  expect(result).toContain('Count: <!-- -->5');
  });

@​astrojs/mdx@​3.0.1

Patch Changes

• #10813 3cc3e2c Thanks @​Xetera! - Omitting compiler-internal symbol from user components to fix breaking error messages

Changelog

Sourced from @​astrojs/mdx's changelog.

3.1.0

Minor Changes

• #11144 803dd80 Thanks @​ematipico! - The integration now exposes a function called getContainerRenderer, that can be used inside the Container APIs to load the relative renderer.

  import { experimental_AstroContainer as AstroContainer } from 'astro/container';
  import ReactWrapper from '../src/components/ReactWrapper.astro';
  import { loadRenderers } from 'astro:container';
  import { getContainerRenderer } from '@astrojs/react';
  test('ReactWrapper with react renderer', async () => {
  const renderers = await loadRenderers([getContainerRenderer()]);
  const container = await AstroContainer.create({
  renderers,
  });
  const result = await container.renderToString(ReactWrapper);
  expect(result).toContain('Counter');
  expect(result).toContain('Count: <!-- -->5');
  });

3.0.1

Patch Changes

• #10813 3cc3e2c Thanks @​Xetera! - Omitting compiler-internal symbol from user components to fix breaking error messages

Commits

• 48d5309 [ci] release (#11186)
• 803dd80 feat(container): provide a virtual module to load renderers (#11144)
• 464b0a1 fix(deps): update all non-major dependencies (#11151)
• 9ddd638 [ci] release (#11086)
• 3cc3e2c fix(renderer): omitting internal symbol from mdx props (#10813)
• cb2586f fix(deps): update all non-major dependencies (#11015)
• See full diff in compare view

Updates @astrojs/sitemap from 3.1.4 to 3.1.5

Release notes

Sourced from @​astrojs/sitemap's releases.

@​astrojs/sitemap@​3.1.5

Patch Changes

• #10779 cefeadf Thanks @​adrianlyjak! - Fixes false positives for status code routes like 404 and 500 when generating sitemaps.

Changelog

Sourced from @​astrojs/sitemap's changelog.

3.1.5

Patch Changes

• #10779 cefeadf Thanks @​adrianlyjak! - Fixes false positives for status code routes like 404 and 500 when generating sitemaps.

Commits

• 9ddd638 [ci] release (#11086)
• cefeadf Make status code check more strict for sitemap plugin (#10779)
• f9b6f4f chore(deps): update all non-major dependencies (#10958)
• 05d58ef fix(deps): update all non-major dependencies (#10901)
• 8d5f3e8 chore(deps): update all non-major dependencies (#10833)
• 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

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml