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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated.
next
is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exit
onnext
.Releases
astro@5.0.0-alpha.0
Major Changes
#10742
b6fbdaa
Thanks @ematipico! - The lowest version of Node supported by Astro is now Node v18.17.1 and higher.#11715
d74617c
Thanks @Princesseuh! - Refactor the exported types from theastro
module. There should normally be no breaking changes, but if you relied on some previously deprecated types, these might now have been fully removed.In most cases, updating your code to move away from previously deprecated APIs in previous versions of Astro should be enough to fix any issues.
#11660
e90f559
Thanks @bluwy! - Fixes attribute rendering for non-boolean HTML attributes with boolean values to match proper attribute handling in browsers.Previously, non-boolean attributes may not have included their values when rendered to HTML. In Astro v5.0, the values are now explicitly rendered as
="true"
or="false"
In the following
.astro
examples, onlyallowfullscreen
is a boolean attribute:Astro v5.0 now preserves the full data attribute with its value when rendering the HTML of non-boolean attributes:
If you rely on attribute values, for example to locate elements or to conditionally render, update your code to match the new non-boolean attribute values:
#11714
8a53517
Thanks @matthewp! - Remove support for functionPerRouteThis change removes support for the
functionPerRoute
option both in Astro and@astrojs/vercel
.This option made it so that each route got built as separate entrypoints so that they could be loaded as separate functions. The hope was that by doing this it would decrease the size of each function. However in practice routes use most of the same code, and increases in function size limitations made the potential upsides less important.
Additionally there are downsides to functionPerRoute, such as hitting limits on the number of functions per project. The feature also never worked with some Astro features like i18n domains and request rewriting.
Given this, the feature has been removed from Astro.
Patch Changes
#11745
89bab1e
Thanks @bluwy! - Prints prerender dynamic value usage warning only if it's used#11730
2df49a6
Thanks @florian-lefebvre! - Simplifies path operations ofastro sync
Updated dependencies [
83a2a64
]:@astrojs/vercel@8.0.0-alpha.0
Major Changes
#11714
8a53517
Thanks @matthewp! - Remove support for functionPerRouteThis change removes support for the
functionPerRoute
option both in Astro and@astrojs/vercel
.This option made it so that each route got built as separate entrypoints so that they could be loaded as separate functions. The hope was that by doing this it would decrease the size of each function. However in practice routes use most of the same code, and increases in function size limitations made the potential upsides less important.
Additionally there are downsides to functionPerRoute, such as hitting limits on the number of functions per project. The feature also never worked with some Astro features like i18n domains and request rewriting.
Given this, the feature has been removed from Astro.
Minor Changes
#11728
5ea02b1
Thanks @matthewp! - Deprecates thefunctionPerRoute
optionThis option is now deprecated, and will be removed entirely in Astro v5.0. We suggest removing this option from your configuration as soon as you are able to:
import { defineConfig } from 'astro/config'; import vercel from '@astrojs/vercel/serverless'; export default defineConfig({ // ... output: 'server', adapter: vercel({ - functionPerRoute: true, }), });
Patch Changes
b6fbdaa
,89bab1e
,d74617c
,e90f559
,2df49a6
,8a53517
]:@astrojs/markdown-remark@6.0.0-alpha.0
Major Changes
#11661
83a2a64
Thanks @bluwy! - Renames the following CSS variables theme color token names to better align with the Shiki v1 defaults:--astro-code-color-text
=>--astro-code-foreground
--astro-code-color-background
=>--astro-code-background
You can perform a global find and replace in your project to migrate to the new token names.
create-astro@4.8.4-alpha.0
Patch Changes
d12dcbf
Thanks @bluwy! - Fixes initial git commit when initializing git@astrojs/markdoc@1.0.0-alpha.0
Patch Changes
b6fbdaa
,89bab1e
,d74617c
,83a2a64
,e90f559
,2df49a6
,8a53517
]:@astrojs/mdx@4.0.0-alpha.0
Patch Changes
#11717
423614e
Thanks @bluwy! - Fixes stack trace location when failed to parse an MDX file with frontmatterUpdated dependencies [
b6fbdaa
,89bab1e
,d74617c
,83a2a64
,e90f559
,2df49a6
,8a53517
]:@astrojs/node@9.0.0-alpha.0
Patch Changes
b6fbdaa
,89bab1e
,d74617c
,e90f559
,2df49a6
,8a53517
]:@astrojs/svelte@6.0.0-alpha.0
Patch Changes
b6fbdaa
,89bab1e
,d74617c
,e90f559
,2df49a6
,8a53517
]:@astrojs/tailwind@6.0.0-alpha.0
Patch Changes
b6fbdaa
,89bab1e
,d74617c
,e90f559
,2df49a6
,8a53517
]:@astrojs/vue@5.0.0-alpha.0
Patch Changes
b6fbdaa
,89bab1e
,d74617c
,e90f559
,2df49a6
,8a53517
]: