Bump astro from 5.4.2 to 5.5.2

[dependabot]

Bumps astro from 5.4.2 to 5.5.2.

Release notes

Sourced from astro's releases.

[email protected]

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.

[email protected]

Patch Changes

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

[email protected]

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

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)