build(deps): bump astro from 4.11.0 to 4.13.3 in /website

[dependabot]

Bumps astro from 4.11.0 to 4.13.3.

Release notes

Sourced from astro's releases.

[email protected]

Patch Changes

• #11653 32be549 Thanks @​florian-lefebvre! - Updates astro:env docs to reflect current developments and usage guidance

• #11658 13b912a Thanks @​bholmesdev! - Fixes orThrow() type when calling an Action without an input validator.

• #11603 f31d466 Thanks @​bholmesdev! - Improves user experience when render an Action result from a form POST request:

  • Removes "Confirm post resubmission?" dialog when refreshing a result.
  • Removes the ?_astroAction=NAME flag when a result is rendered.

  Also improves the DX of directing to a new route on success. Actions will now redirect to the route specified in your action string on success, and redirect back to the previous page on error. This follows the routing convention of established backend frameworks like Laravel.

  For example, say you want to redirect to a /success route when actions.signup succeeds. You can add /success to your action string like so:

  <form method="POST" action={'/success' + actions.signup}></form>

  • On success, Astro will redirect to /success.
  • On error, Astro will redirect back to the current page.

  You can retrieve the action result from either page using the Astro.getActionResult() function.

  Note on security

  This uses a temporary cookie to forward the action result to the next page. The cookie will be deleted when that page is rendered.

  ⚠ The action result is not encrypted. In general, we recommend returning minimal data from an action handler to a) avoid leaking sensitive information, and b) avoid unexpected render issues once the temporary cookie is deleted. For example, a login function may return a user's session id to retrieve from your Astro frontmatter, rather than the entire user object.

[email protected]

Patch Changes

• #11648 589d351 Thanks @​bholmesdev! - Fixes unexpected error when refreshing a POST request from a form using Actions.

• #11600 09ec2ca Thanks @​ArmandPhilippot! - Deprecates getEntryBySlug and getDataEntryById functions exported by astro:content in favor of getEntry.

• #11593 81d7150 Thanks @​bholmesdev! - Adds support for Date(), Map(), and Set() from action results. See devalue for a complete list of supported values.

  Also fixes serialization exceptions when deploying Actions with edge middleware on Netlify and Vercel.

• #11617 196092a Thanks @​abubakriz! - Fix toolbar audit incorrectly flagging images as above the fold.

• #11634 2716f52 Thanks @​bholmesdev! - Fixes internal server error when calling an Astro Action without arguments on Vercel.

• #11628 9aaf58c Thanks @​madbook! - Ensures consistent CSS chunk hashes across different environments

[email protected]

Patch Changes

... (truncated)

Changelog

Sourced from astro's changelog.

4.13.3

Patch Changes

• #11653 32be549 Thanks @​florian-lefebvre! - Updates astro:env docs to reflect current developments and usage guidance

• #11658 13b912a Thanks @​bholmesdev! - Fixes orThrow() type when calling an Action without an input validator.

• #11603 f31d466 Thanks @​bholmesdev! - Improves user experience when render an Action result from a form POST request:

  • Removes "Confirm post resubmission?" dialog when refreshing a result.
  • Removes the ?_astroAction=NAME flag when a result is rendered.

  Also improves the DX of directing to a new route on success. Actions will now redirect to the route specified in your action string on success, and redirect back to the previous page on error. This follows the routing convention of established backend frameworks like Laravel.

  For example, say you want to redirect to a /success route when actions.signup succeeds. You can add /success to your action string like so:

  <form method="POST" action={'/success' + actions.signup}></form>

  • On success, Astro will redirect to /success.
  • On error, Astro will redirect back to the current page.

  You can retrieve the action result from either page using the Astro.getActionResult() function.

  Note on security

  This uses a temporary cookie to forward the action result to the next page. The cookie will be deleted when that page is rendered.

  ⚠ The action result is not encrypted. In general, we recommend returning minimal data from an action handler to a) avoid leaking sensitive information, and b) avoid unexpected render issues once the temporary cookie is deleted. For example, a login function may return a user's session id to retrieve from your Astro frontmatter, rather than the entire user object.

4.13.2

Patch Changes

• #11648 589d351 Thanks @​bholmesdev! - Fixes unexpected error when refreshing a POST request from a form using Actions.

• #11600 09ec2ca Thanks @​ArmandPhilippot! - Deprecates getEntryBySlug and getDataEntryById functions exported by astro:content in favor of getEntry.

• #11593 81d7150 Thanks @​bholmesdev! - Adds support for Date(), Map(), and Set() from action results. See devalue for a complete list of supported values.

  Also fixes serialization exceptions when deploying Actions with edge middleware on Netlify and Vercel.

• #11617 196092a Thanks @​abubakriz! - Fix toolbar audit incorrectly flagging images as above the fold.

• #11634 2716f52 Thanks @​bholmesdev! - Fixes internal server error when calling an Astro Action without arguments on Vercel.

• #11628 9aaf58c Thanks @​madbook! - Ensures consistent CSS chunk hashes across different environments

... (truncated)

Commits

• 8118120 [ci] release (#11654)
• ee69a06 [ci] format
• f31d466 Actions: auto-redirect action response to avoid "confirm form resubmission" d...
• 7adb350 Prevent throwing in react and solid component checks (#11624)
• 13b912a Actions: fix missing orThrow type when input is omitted (#11658)
• a851021 [ci] format
• 32be549 chore: improve astro:env docs (#11653)
• 6b99523 [ci] release (#11602)
• 589d351 Actions: remove "action used with get" error (#11648)
• 72c7ae9 update formatter config (#11640)
• 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)

[dependabot]

Superseded by #137.