Bumps the devdependencies group with 1 update: [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro). Updates `astro` from 5.12.8 to 5.13.2 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/withastro/astro/releases">astro's releases</a>.</em></p> <blockquote> <h2>astro@5.13.2</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://github.com/withastro/astro/commit/4d16de7f95db5d1ec1ce88610d2a95e606e83820"><code>4d16de7</code></a> Thanks <a href="https://github.com/ematipico"><code>@ematipico</code></a>! - Improves the detection of remote paths in the <code>_image</code> endpoint. Now <code>href</code> parameters that start with <code>//</code> are considered remote paths.</p> </li> <li> <p>Updated dependencies [<a href="https://github.com/withastro/astro/commit/4d16de7f95db5d1ec1ce88610d2a95e606e83820"><code>4d16de7</code></a>]:</p> <ul> <li><code>@astrojs/internal-helpers</code><a href="https://github.com/0"><code>@0</code></a>.7.2</li> <li><code>@astrojs/markdown-remark</code><a href="https://github.com/6"><code>@6</code></a>.3.6</li> </ul> </li> </ul> <h2>astro@5.13.1</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/withastro/astro/pull/14225">#14225</a> <a href="https://github.com/withastro/astro/commit/f2490aba420a8999c0e8d12b9e1e69d4e33ae29e"><code>f2490ab</code></a> Thanks <a href="https://github.com/delucis"><code>@delucis</code></a>! - Fixes the <code>experimental.chromeDevtoolsWorkspace</code> feature.</li> </ul> <h2>astro@5.13.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/14173">#14173</a> <a href="https://github.com/withastro/astro/commit/39911b823d4617d99cc95e4b7584e9e4b7b90038"><code>39911b8</code></a> Thanks <a href="https://github.com/florian-lefebvre"><code>@florian-lefebvre</code></a>! - Adds an experimental flag <code>staticImportMetaEnv</code> to disable the replacement of <code>import.meta.env</code> values with <code>process.env</code> calls and their coercion of environment variable values. This supersedes the <code>rawEnvValues</code> experimental flag, which is now removed.</p> <p>Astro allows you to configure a <a href="https://docs.astro.build/en/guides/environment-variables/#type-safe-environment-variables">type-safe schema for your environment variables</a>, and converts variables imported via <code>astro:env</code> into the expected type. This is the recommended way to use environment variables in Astro, as it allows you to easily see and manage whether your variables are public or secret, available on the client or only on the server at build time, and the data type of your values.</p> <p>However, you can still access environment variables through <code>process.env</code> and <code>import.meta.env</code> directly when needed. This was the only way to use environment variables in Astro before <code>astro:env</code> was added in Astro 5.0, and Astro's default handling of <code>import.meta.env</code> includes some logic that was only needed for earlier versions of Astro.</p> <p>The <code>experimental.staticImportMetaEnv</code> flag updates the behavior of <code>import.meta.env</code> to align with <a href="https://vite.dev/guide/env-and-mode.html#env-variables">Vite's handling of environment variables</a> and for better ease of use with Astro's current implementations and features. <strong>This will become the default behavior in Astro 6.0</strong>, and this early preview is introduced as an experimental feature.</p> <p>Currently, non-public <code>import.meta.env</code> environment variables are replaced by a reference to <code>process.env</code>. Additionally, Astro may also convert the value type of your environment variables used through <code>import.meta.env</code>, which can prevent access to some values such as the strings <code>"true"</code> (which is converted to a boolean value), and <code>"1"</code> (which is converted to a number).</p> <p>The <code>experimental.staticImportMetaEnv</code> flag simplifies Astro's default behavior, making it easier to understand and use. Astro will no longer replace any <code>import.meta.env</code> environment variables with a <code>process.env</code> call, nor will it coerce values.</p> <p>To enable this feature, add the experimental flag in your Astro config and remove <code>rawEnvValues</code> if it was enabled:</p> <pre lang="diff"><code>// astro.config.mjs import { defineConfig } from "astro/config"; <p>export default defineConfig({</p> <ul> <li>experimental: {</li> <li>staticImportMetaEnv: true</li> </ul> <ul> <li>rawEnvValues: false</li> </ul> <ul> <li>} }); </code></pre></li> </ul> <h4>Updating your project</h4> <p>If you were relying on Astro's default coercion, you may need to update your project code to apply it manually:</p> <pre lang="diff"><code>// src/components/MyComponent.astro - const enabled: boolean = import.meta.env.ENABLED; </code></pre> </li> </ul>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md">astro's changelog</a>.</em></p> <blockquote> <h2>5.13.2</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://github.com/withastro/astro/commit/4d16de7f95db5d1ec1ce88610d2a95e606e83820"><code>4d16de7</code></a> Thanks <a href="https://github.com/ematipico"><code>@ematipico</code></a>! - Improves the detection of remote paths in the <code>_image</code> endpoint. Now <code>href</code> parameters that start with <code>//</code> are considered remote paths.</p> </li> <li> <p>Updated dependencies [<a href="https://github.com/withastro/astro/commit/4d16de7f95db5d1ec1ce88610d2a95e606e83820"><code>4d16de7</code></a>]:</p> <ul> <li><code>@astrojs/internal-helpers</code><a href="https://github.com/0"><code>@0</code></a>.7.2</li> <li><code>@astrojs/markdown-remark</code><a href="https://github.com/6"><code>@6</code></a>.3.6</li> </ul> </li> </ul> <h2>5.13.1</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/withastro/astro/pull/14225">#14225</a> <a href="https://github.com/withastro/astro/commit/f2490aba420a8999c0e8d12b9e1e69d4e33ae29e"><code>f2490ab</code></a> Thanks <a href="https://github.com/delucis"><code>@delucis</code></a>! - Fixes the <code>experimental.chromeDevtoolsWorkspace</code> feature.</li> </ul> <h2>5.13.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/14173">#14173</a> <a href="https://github.com/withastro/astro/commit/39911b823d4617d99cc95e4b7584e9e4b7b90038"><code>39911b8</code></a> Thanks <a href="https://github.com/florian-lefebvre"><code>@florian-lefebvre</code></a>! - Adds an experimental flag <code>staticImportMetaEnv</code> to disable the replacement of <code>import.meta.env</code> values with <code>process.env</code> calls and their coercion of environment variable values. This supersedes the <code>rawEnvValues</code> experimental flag, which is now removed.</p> <p>Astro allows you to configure a <a href="https://docs.astro.build/en/guides/environment-variables/#type-safe-environment-variables">type-safe schema for your environment variables</a>, and converts variables imported via <code>astro:env</code> into the expected type. This is the recommended way to use environment variables in Astro, as it allows you to easily see and manage whether your variables are public or secret, available on the client or only on the server at build time, and the data type of your values.</p> <p>However, you can still access environment variables through <code>process.env</code> and <code>import.meta.env</code> directly when needed. This was the only way to use environment variables in Astro before <code>astro:env</code> was added in Astro 5.0, and Astro's default handling of <code>import.meta.env</code> includes some logic that was only needed for earlier versions of Astro.</p> <p>The <code>experimental.staticImportMetaEnv</code> flag updates the behavior of <code>import.meta.env</code> to align with <a href="https://vite.dev/guide/env-and-mode.html#env-variables">Vite's handling of environment variables</a> and for better ease of use with Astro's current implementations and features. <strong>This will become the default behavior in Astro 6.0</strong>, and this early preview is introduced as an experimental feature.</p> <p>Currently, non-public <code>import.meta.env</code> environment variables are replaced by a reference to <code>process.env</code>. Additionally, Astro may also convert the value type of your environment variables used through <code>import.meta.env</code>, which can prevent access to some values such as the strings <code>"true"</code> (which is converted to a boolean value), and <code>"1"</code> (which is converted to a number).</p> <p>The <code>experimental.staticImportMetaEnv</code> flag simplifies Astro's default behavior, making it easier to understand and use. Astro will no longer replace any <code>import.meta.env</code> environment variables with a <code>process.env</code> call, nor will it coerce values.</p> <p>To enable this feature, add the experimental flag in your Astro config and remove <code>rawEnvValues</code> if it was enabled:</p> <pre lang="diff"><code>// astro.config.mjs import { defineConfig } from "astro/config"; <p>export default defineConfig({</p> <ul> <li>experimental: {</li> <li>staticImportMetaEnv: true</li> </ul> <ul> <li>rawEnvValues: false</li> </ul> <ul> <li>} }); </code></pre></li> </ul> <h4>Updating your project</h4> <p>If you were relying on Astro's default coercion, you may need to update your project code to apply it manually:</p> </li> </ul>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/withastro/astro/commit/92881331d1138ae146bbc4b0bfb9c675ca3f3d55"><code>9288133</code></a> [ci] release (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14232">#14232</a>)</li> <li><a href="https://github.com/withastro/astro/commit/1040510a0c087c644c8f75d58b28917d4f96cbf9"><code>1040510</code></a> [ci] format</li> <li><a href="https://github.com/withastro/astro/commit/4d16de7f95db5d1ec1ce88610d2a95e606e83820"><code>4d16de7</code></a> Merge commit from fork</li> <li><a href="https://github.com/withastro/astro/commit/1591bc70ce6e5636e20a1cf8eab16ec95484816b"><code>1591bc7</code></a> [ci] release (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14227">#14227</a>)</li> <li><a href="https://github.com/withastro/astro/commit/f2490aba420a8999c0e8d12b9e1e69d4e33ae29e"><code>f2490ab</code></a> Fix automatic Chrome DevTools workspace feature (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14225">#14225</a>)</li> <li><a href="https://github.com/withastro/astro/commit/a186848c34615dab5816df3bd8962ba16314f2b9"><code>a186848</code></a> [ci] release (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14217">#14217</a>)</li> <li><a href="https://github.com/withastro/astro/commit/b33780d8bf925bfddfb66105f4d46195d7fb0206"><code>b33780d</code></a> [ci] format</li> <li><a href="https://github.com/withastro/astro/commit/39911b823d4617d99cc95e4b7584e9e4b7b90038"><code>39911b8</code></a> feat: experimental static import.meta.env (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14173">#14173</a>)</li> <li><a href="https://github.com/withastro/astro/commit/41ed3ac54adf1025a38031757ee0bfaef8504092"><code>41ed3ac</code></a> feat: add automatic chrome workspace handling (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14122">#14122</a>)</li> <li><a href="https://github.com/withastro/astro/commit/806d2dc538089dd1e38623d35e75c5a6490a2494"><code>806d2dc</code></a> chore: add additional contributor to changelog (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14203">#14203</a>)</li> <li>Additional commits viewable in <a href="https://github.com/withastro/astro/commits/astro@5.13.2/packages/astro">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=astro&package-manager=npm_and_yarn&previous-version=5.12.8&new-version=5.13.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 </details>
-Original file line number
+Diff line change
 		"@astrojs/check": "0.9.4",
 		"@astrojs/svelte": "7.1.0",
 		"@guardian/libs": "workspace:*",
 -		"astro": "5.12.8",
 +		"astro": "5.13.2",
 		"svelte": "5.38.0",
 		"typescript": "5.5.2",
 		"wireit": "0.14.12"