fix(deps): update dependency astro to ^4.11.3 #93
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.9.2
->^4.11.3
Release Notes
withastro/astro (astro)
v4.11.3
Compare Source
Patch Changes
#11347
33bdc54
Thanks @bluwy! - Fixes installed packages detection when runningastro check
#11327
0df8142
Thanks @ematipico! - Fixes an issue with the container APIs where a runtime error was thrown during the build, when usingpnpm
as package manager.v4.11.2
Compare Source
Patch Changes
#11335
4c4741b
Thanks @ematipico! - Reverts #11292, which caused a regression to the input type#11326
41121fb
Thanks @florian-lefebvre! - Fixes a case where runningastro sync
when using the experimentalastro:env
feature would fail if environment variables were missing#11338
9752a0b
Thanks @zaaakher! - Fixes svg icon margin in devtool tooltip title to look coherent inrtl
andltr
layouts#11331
f1b78a4
Thanks @bluwy! - Removesresolve
package and simplify internal resolve check#11339
8fdbf0e
Thanks @matthewp! - Remove non-fatal errors from telemetryPreviously we tracked non-fatal errors in telemetry to get a good idea of the types of errors that occur in
astro dev
. However this has become noisy over time and results in a lot of data that isn't particularly useful. This removes those non-fatal errors from being tracked.v4.11.1
Compare Source
Patch Changes
#11308
44c61dd
Thanks @ematipico! - Fixes an issue where custom404.astro
and500.astro
were not returning the correct status code when rendered inside a rewriting cycle.#11302
0622567
Thanks @martrapp! - Fixes an issue with the view transition router when redirecting to an URL with different origin.Updated dependencies [
b6afe6a
,41064ce
]:v4.11.0
Compare Source
Minor Changes
#11197
4b46bd9
Thanks @braebo! - AddsShikiTransformer
support to the<Code />
component with a newtransformers
prop.Note that
transformers
only applies classes and you must provide your own CSS rules to target the elements of your code block.v4.10.3
Compare Source
Patch Changes
#11213
94ac7ef
Thanks @florian-lefebvre! - Removes thePUBLIC_
prefix constraint forastro:env
public variables#11213
94ac7ef
Thanks @florian-lefebvre! - BREAKING CHANGE to the experimentalastro:env
feature onlyServer secrets specified in the schema must now be imported from
astro:env/server
. UsinggetSecret()
is no longer required to use these environment variables in your schema:Note that using
getSecret()
with these keys is still possible, but no longer involves any special handling and the raw value will be returned, just like retrieving secrets not specified in your schema.#11234
4385bf7
Thanks @ematipico! - Adds a new function calledaddServerRenderer
to the Container API. Use this function to manually store renderers inside the instance of your container.This new function should be preferred when using the Container API in environments like on-demand pages:
#11249
de60c69
Thanks @markgaze! - Fixes a performance issue with JSON schema generation#11242
e4fc2a0
Thanks @ematipico! - Fixes a case where the virtual moduleastro:container
wasn't resolved#11236
39bc3a5
Thanks @ascorbic! - Fixes a case where symlinked content collection directories were not correctly resolved#11258
d996db6
Thanks @ascorbic! - Adds a new errorRewriteWithBodyUsed
that throws whenAstro.rewrite
is used after the request body has already been read.#11243
ba2b14c
Thanks @V3RON! - Fixes a prerendering issue for libraries innode_modules
when a folder with an underscore is in the path.#11244
d07d2f7
Thanks @ematipico! - Improves the developer experience of the custom500.astro
page in development mode.Before, in development, an error thrown during the rendering phase would display the default error overlay, even when users had the
500.astro
page.Now, the development server will display the
500.astro
and the original error is logged in the console.#11240
2851b0a
Thanks @ascorbic! - Ignores query strings in module identifiers when matching ".astro" file extensions in Vite plugin#11245
e22be22
Thanks @bluwy! - Refactors prerendering chunk handling to correctly remove unused code during the SSR runtimev4.10.2
Compare Source
Patch Changes
#11231
58d7dbb
Thanks @ematipico! - Fixes a regression forgetViteConfig
, where the inline config wasn't merged in the final config.#11228
1e293a1
Thanks @ascorbic! - UpdatesgetCollection()
to always return a cloned array#11207
7d9aac3
Thanks @ematipico! - Fixes an issue in the rewriting logic where old data was not purged during the rewrite flow. This caused some false positives when checking the validity of URL path names during the rendering phase.#11189
75a8fe7
Thanks @ematipico! - Improve error message when usinggetLocaleByPath
on path that doesn't contain any locales.#11195
0a6ab6f
Thanks @florian-lefebvre! - Adds support for enums toastro:env
You can now call
envField.enum
:#11210
66fc028
Thanks @matthewp! - Close the iterator only after rendering is complete#11195
0a6ab6f
Thanks @florian-lefebvre! - Adds additional validation options toastro:env
astro:env
schema datatypesstring
andnumber
now have new optional validation rules:#11211
97724da
Thanks @matthewp! - Let middleware handle the original request URL#10607
7327c6a
Thanks @frankbits! - Fixes an issue where a leading slash created incorrect conflict resolution between pages generated from static routes and catch-all dynamic routesv4.10.1
Compare Source
Patch Changes
#11198
8b9a499
Thanks @florian-lefebvre! - Fixes a case whereastro:env
getSecret
would not retrieve environment variables properly in dev and build modes#11206
734b98f
Thanks @florian-lefebvre! - BREAKING CHANGE to the experimentalastro:env
feature onlyUpdates the adapter
astro:env
entrypoint fromastro:env/setup
toastro/env/setup
#11205
8c45391
Thanks @Nin3lee! - Fixes a typo in the config referencev4.10.0
Compare Source
Minor Changes
#10974
2668ef9
Thanks @florian-lefebvre! - Adds experimental support for theastro:env
API.The
astro:env
API lets you configure a type-safe schema for your environment variables, and indicate whether they should be available on the server or the client. Import and use your defined variables from the appropriate/client
or/server
module:v4.9.3
Compare Source
Patch Changes
#11171
ff8004f
Thanks @Princesseuh! - Guard globalThis.astroAsset usage in proxy code to avoid errors in wonky situations#11178
1734c49
Thanks @theoephraim! - ImprovesisPromise
utility to check the presence ofthen
on an object before trying to access it - which can cause undesired side-effects on Proxy objects#11183
3cfa2ac
Thanks @66Leo66! - Suggestpnpm dlx
instead ofpnpx
in update check.#11147
2d93902
Thanks @kitschpatrol! - Fixes invalid MIME types in Picture source elements for jpg and svg extensions, which was preventing otherwise valid source variations from being shown by the browser#11141
19df89f
Thanks @ematipico! - Fixes an internal error that prevented theAstroContainer
to render theContent
component.You can now write code similar to the following to render content collections:
#11170
ba20c71
Thanks @matthewp! - Retain client scripts in content cacheConfiguration
📅 Schedule: Branch creation - "before 10am on the first day of the month" in timezone GMT, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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 has been generated by Mend Renovate. View repository job log here.