chore(deps): bump the all group with 2 updates

[dependabot]

Bumps the all group with 2 updates: astro and tailwindcss.

Updates astro from 4.13.1 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

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

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

Updates tailwindcss from 3.4.7 to 3.4.9

Release notes

Sourced from tailwindcss's releases.

v3.4.9

Fixed

• No longer warns when broad glob patterns are detecting vendor folders

v3.4.8

Fixed

• Fix minification when using nested CSS (#14105)
• Warn when broad glob patterns are used in the content configuration (#14140)

Changelog

Sourced from tailwindcss's changelog.

[3.4.9] - 2024-08-08

Fixed

• No longer warns when broad glob patterns are detecting vendor folders

[3.4.8] - 2024-08-07

Fixed

• Fix minification when using nested CSS (#14105)
• Warn when broad glob patterns are used in the content configuration (#14140)

Commits

• f65023e 3.4.9
• 702ba6a Don't warn about broad globs in vendor folders (#14147)
• 1676118 3.4.8
• 69c81f2 rename master to main
• 858696a Warn when broad glob patterns are used in the content configuration (#14140)
• 1f23c2e Bump to latest cssnano v6 (#14105)
• 28bd90e Automate checksum generation for standalone CLI (#14081)
• 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 <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

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.