Bump astro from 5.0.0-beta.5 to 5.0.0-beta.6

[dependabot]

Bumps astro from 5.0.0-beta.5 to 5.0.0-beta.6.

Release notes

Sourced from astro's releases.

[email protected]

Major Changes

• #12268 4e9a3ac Thanks @​ematipico! - The command astro add vercel now updates the configuration file differently, and adds @astrojs/vercel as module to import.

  This is a breaking change because it requires the version 8.* of @astrojs/vercel.

• #12231 90ae100 Thanks @​bluwy! - Updates the automatic charset=utf-8 behavior for Markdown pages, where instead of responding with charset=utf-8 in the Content-Type header, Astro will now automatically add the <meta charset="utf-8"> tag instead.

  This behaviour only applies to Markdown pages (.md or similar Markdown files located within src/pages/) that do not use Astro's special layout frontmatter property. It matches the rendering behaviour of other non-content pages, and retains the minimal boilerplate needed to write with non-ASCII characters when adding individual Markdown pages to your site.

  If your Markdown pages use the layout frontmatter property, then HTML encoding will be handled by the designated layout component instead, and the <meta charset="utf-8"> tag will not be added to your page by default.

  If you require charset=utf-8 to render your page correctly, make sure that your layout components contain the <meta charset="utf-8"> tag. You may need to add this if you have not already done so.

Minor Changes

• #12243 eb41d13 Thanks @​florian-lefebvre! - Improves defineConfig type safety. TypeScript will now error if a group of related configuration options do not have consistent types. For example, you will now see an error if your language set for i18n.defaultLocale is not one of the supported locales specified in i18n.locales.

• #12150 93351bc Thanks @​bluwy! - Adds support for passing values other than "production" or "development" to the --mode flag (e.g. "staging", "testing", or any custom value) to change the value of import.meta.env.MODE or the loaded .env file. This allows you take advantage of Vite's mode feature.

  Also adds a new --devOutput flag for astro build that will output a development-based build.

  Note that changing the mode does not change the kind of code transform handled by Vite and Astro:

  • In astro dev, Astro will transform code with debug information.
  • In astro build, Astro will transform code with the most optimized output and removes debug information.
  • In astro build --devOutput (new flag), Astro will transform code with debug information like in astro dev.

  This enables various usecases like:

  # Run the dev server connected to a "staging" API
  astro dev --mode staging
  Build a site that connects to a "staging" API
  astro build --mode staging
  Build a site that connects to a "production" API with additional debug information
  astro build --devOutput
  Build a site that connects to a "testing" API
  astro build --mode testing

  The different modes can be used to load different .env files, e.g. .env.staging or .env.production, which can be customized for each environment, for example with different API_URL environment variable values.

Patch Changes

• #12302 7196c24 Thanks @​ematipico! - Fixes an issue where the origin check middleware run for prendered pages

... (truncated)

Changelog

Sourced from astro's changelog.

5.0.0-beta.6

Major Changes

• #12268 4e9a3ac Thanks @​ematipico! - The command astro add vercel now updates the configuration file differently, and adds @astrojs/vercel as module to import.

  This is a breaking change because it requires the version 8.* of @astrojs/vercel.

• #12231 90ae100 Thanks @​bluwy! - Updates the automatic charset=utf-8 behavior for Markdown pages, where instead of responding with charset=utf-8 in the Content-Type header, Astro will now automatically add the <meta charset="utf-8"> tag instead.

  This behaviour only applies to Markdown pages (.md or similar Markdown files located within src/pages/) that do not use Astro's special layout frontmatter property. It matches the rendering behaviour of other non-content pages, and retains the minimal boilerplate needed to write with non-ASCII characters when adding individual Markdown pages to your site.

  If your Markdown pages use the layout frontmatter property, then HTML encoding will be handled by the designated layout component instead, and the <meta charset="utf-8"> tag will not be added to your page by default.

  If you require charset=utf-8 to render your page correctly, make sure that your layout components contain the <meta charset="utf-8"> tag. You may need to add this if you have not already done so.

Minor Changes

• #12243 eb41d13 Thanks @​florian-lefebvre! - Improves defineConfig type safety. TypeScript will now error if a group of related configuration options do not have consistent types. For example, you will now see an error if your language set for i18n.defaultLocale is not one of the supported locales specified in i18n.locales.

• #12150 93351bc Thanks @​bluwy! - Adds support for passing values other than "production" or "development" to the --mode flag (e.g. "staging", "testing", or any custom value) to change the value of import.meta.env.MODE or the loaded .env file. This allows you take advantage of Vite's mode feature.

  Also adds a new --devOutput flag for astro build that will output a development-based build.

  Note that changing the mode does not change the kind of code transform handled by Vite and Astro:

  • In astro dev, Astro will transform code with debug information.
  • In astro build, Astro will transform code with the most optimized output and removes debug information.
  • In astro build --devOutput (new flag), Astro will transform code with debug information like in astro dev.

  This enables various usecases like:

  # Run the dev server connected to a "staging" API
  astro dev --mode staging
  Build a site that connects to a "staging" API
  astro build --mode staging
  Build a site that connects to a "production" API with additional debug information
  astro build --devOutput
  Build a site that connects to a "testing" API
  astro build --mode testing

  The different modes can be used to load different .env files, e.g. .env.staging or .env.production, which can be customized for each environment, for example with different API_URL environment variable values.

Patch Changes

... (truncated)

Commits

• 731b697 [ci] release (beta) (#12250)
• d879c02 Fix merge error
• 63b4ab9 Merge branch 'main' into next
• 5f7bf49 [ci] release (#12290)
• ffc836b Fix cli command typo (#12342)
• c414eec [ci] format
• 9ca89b3 fix(cli): reset NODE_ENV to ensure install command run in dev mode (#12338)
• c1786d6 fix(i18n): default locale in server islands (#12341)
• e2056c2 [ci] format
• ea85546 Fix base not working with server actions (#12280)
• 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)