Bump astro from 4.16.8 to 4.16.13 in /docs

[dependabot[bot]]

Bumps astro from 4.16.8 to 4.16.13.

Release notes

Sourced from astro's releases.

astro@4.16.13

Patch Changes

• #12436 453ec6b Thanks @​martrapp! - Fixes a potential null access in the clientside router

• #12392 0462219 Thanks @​apatel369! - Fixes an issue where scripts were not correctly injected during the build. The issue was triggered when there were injected routes with the same entrypoint and different pattern

astro@4.16.12

Patch Changes

• #12420 acac0af Thanks @​ematipico! - Fixes an issue where the dev server returns a 404 status code when a user middleware returns a valid Response.

astro@4.16.11

Patch Changes

• #12305 f5f7109 Thanks @​florian-lefebvre! - Fixes a case where the error overlay would not escape the message

• #12402 823e73b Thanks @​ematipico! - Fixes a case where Astro allowed to call an action without using Astro.callAction. This is now invalid, and Astro will show a proper error.

  ---
  import { actions } from "astro:actions";
  -const result = actions.getUser({ userId: 123 });
  +const result = Astro.callAction(actions.getUser, { userId: 123 });
  

• #12401 9cca108 Thanks @​bholmesdev! - Fixes unexpected 200 status in dev server logs for action errors and redirects.

astro@4.16.10

Patch Changes

• #12311 bf2723e Thanks @​dinesh-58! - Adds checked to the list of boolean attributes.

• #12363 222f718 Thanks @​Fryuni! - Fixes code generated by astro add command when adding a version of an integration other than the default latest.

• #12368 493fe43 Thanks @​bluwy! - Improves error logs when executing commands

• #12355 c4726d7 Thanks @​apatel369! - Improves error reporting for invalid frontmatter in MDX files during the astro build command. The error message now includes the file path where the frontmatter parsing failed.

astro@4.16.9

Patch Changes

• #12333 836cd91 Thanks @​imattacus! - Destroy the server response stream if async error is thrown

• #12358 7680349 Thanks @​spacedawwwg! - Honors inlineAstroConfig parameter in getViteConfig when creating a logger

• #12353 35795a1 Thanks @​hippotastic! - Fixes an issue in dev server watch file handling that could cause multiple restarts for a single file change.

... (truncated)

Changelog

Sourced from astro's changelog.

4.16.13

Patch Changes

• #12436 453ec6b Thanks @​martrapp! - Fixes a potential null access in the clientside router

• #12392 0462219 Thanks @​apatel369! - Fixes an issue where scripts were not correctly injected during the build. The issue was triggered when there were injected routes with the same entrypoint and different pattern

4.16.12

Patch Changes

• #12420 acac0af Thanks @​ematipico! - Fixes an issue where the dev server returns a 404 status code when a user middleware returns a valid Response.

4.16.11

Patch Changes

• #12305 f5f7109 Thanks @​florian-lefebvre! - Fixes a case where the error overlay would not escape the message

• #12402 823e73b Thanks @​ematipico! - Fixes a case where Astro allowed to call an action without using Astro.callAction. This is now invalid, and Astro will show a proper error.

  ---
  import { actions } from "astro:actions";
  -const result = actions.getUser({ userId: 123 });
  +const result = Astro.callAction(actions.getUser, { userId: 123 });
  

• #12401 9cca108 Thanks @​bholmesdev! - Fixes unexpected 200 status in dev server logs for action errors and redirects.

4.16.10

Patch Changes

• #12311 bf2723e Thanks @​dinesh-58! - Adds checked to the list of boolean attributes.

• #12363 222f718 Thanks @​Fryuni! - Fixes code generated by astro add command when adding a version of an integration other than the default latest.

• #12368 493fe43 Thanks @​bluwy! - Improves error logs when executing commands

• #12355 c4726d7 Thanks @​apatel369! - Improves error reporting for invalid frontmatter in MDX files during the astro build command. The error message now includes the file path where the frontmatter parsing failed.

4.16.9

Patch Changes

• #12333 836cd91 Thanks @​imattacus! - Destroy the server response stream if async error is thrown

... (truncated)

Commits

• 5509117 [ci] release (#12427)
• 453ec6b prevents access to the history state if not set (#12436)
• 9fc2ab8 Update to svelte 5 (#12364)
• bdc0890 [ci] format
• 0462219 Fix script injection during build (#12392)
• 3b3bc9b [ci] release (#12422)
• acac0af fix(routing): middleware in dev (#12420)
• e723e9e [ci] release (#12403)
• 471e712 [ci] format
• 95d52a0 update markdown config docs (#12382)
• 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 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)