build(deps): bump astro from 4.13.0 to 4.13.1 in the astro group

[dependabot[bot]]

Bumps the astro group with 1 update: astro.

Updates astro from 4.13.0 to 4.13.1

Release notes

Sourced from astro's releases.

astro@4.13.1

Patch Changes

• #11584 a65ffe3 Thanks @​bholmesdev! - Removes async local storage dependency from Astro Actions. This allows Actions to run in Cloudflare and Stackblitz without opt-in flags or other configuration.

  This also introduces a new convention for calling actions from server code. Instead of calling actions directly, you must wrap function calls with the new Astro.callAction() utility.

  callAction() is meant to trigger an action from server code. getActionResult() usage with form submissions remains unchanged.

  ---
  import { actions } from 'astro:actions';
  const result = await Astro.callAction(actions.searchPosts, {
  searchTerm: Astro.url.searchParams.get('search'),
  });
  {
  result.data &&
  {
  /* render the results */
  }
  }
  

  Migration

  If you call actions directly from server code, update function calls to use the Astro.callAction() wrapper for pages and context.callAction() for endpoints:

  ---
  import { actions } from 'astro:actions';
  
  const result = await actions.searchPosts({ searchTerm: 'test' });
  
  
  const result = await Astro.callAction(actions.searchPosts, { searchTerm: 'test' });
  
  
  

  If you deploy with Cloudflare and added the nodejs_compat or nodejs_als flags for Actions, we recommend removing these:

  compatibility_flags = [
  - "nodejs_compat",
  - "nodejs_als"
  ]
  

  You can also remove node:async_hooks from the vite.ssr.external option in your astro.config file:

... (truncated)

Changelog

Sourced from astro's changelog.

4.13.1

Patch Changes

• #11584 a65ffe3 Thanks @​bholmesdev! - Removes async local storage dependency from Astro Actions. This allows Actions to run in Cloudflare and Stackblitz without opt-in flags or other configuration.

  This also introduces a new convention for calling actions from server code. Instead of calling actions directly, you must wrap function calls with the new Astro.callAction() utility.

  callAction() is meant to trigger an action from server code. getActionResult() usage with form submissions remains unchanged.

  ---
  import { actions } from 'astro:actions';
  const result = await Astro.callAction(actions.searchPosts, {
  searchTerm: Astro.url.searchParams.get('search'),
  });
  {
  result.data &&
  {
  /* render the results */
  }
  }
  

  Migration

  If you call actions directly from server code, update function calls to use the Astro.callAction() wrapper for pages and context.callAction() for endpoints:

  ---
  import { actions } from 'astro:actions';
  
  const result = await actions.searchPosts({ searchTerm: 'test' });
  
  
  const result = await Astro.callAction(actions.searchPosts, { searchTerm: 'test' });
  
  
  

  If you deploy with Cloudflare and added the nodejs_compat or nodejs_als flags for Actions, we recommend removing these:

  compatibility_flags = [
  - "nodejs_compat",
  - "nodejs_als"
  ]
  

  You can also remove node:async_hooks from the vite.ssr.external option in your astro.config file:

... (truncated)

Commits

• 2abbc28 [ci] release (#11590)
• d052428 [ci] format
• 69d54b4 Remove more unused code (#11598)
• c2d6c1f Remove unused code (#11592)
• ac72ed2 [ci] format
• a65ffe3 Actions: Remove async local storage dependency (#11584)
• 2531abd [ci] format
• 2e9d183 fix: changelog formatting (#11589)
• 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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore 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 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions