fix(deps): update dependency astro to v4.13.3 #59
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.13.2->4.13.3Release Notes
withastro/astro (astro)
v4.13.3Compare Source
Patch Changes
#11653
32be549Thanks @florian-lefebvre! - Updatesastro:envdocs to reflect current developments and usage guidance#11658
13b912aThanks @bholmesdev! - FixesorThrow()type when calling an Action without aninputvalidator.#11603
f31d466Thanks @bholmesdev! - Improves user experience when render an Action result from a form POST request:?_astroAction=NAMEflag 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
actionstring 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
/successroute whenactions.signupsucceeds. You can add/successto youractionstring like so:/success.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
loginfunction may return a user's session id to retrieve from your Astro frontmatter, rather than the entire user object.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.