-
Notifications
You must be signed in to change notification settings - Fork 0
chore(deps): update astro monorepo (major) #306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate
wants to merge
1
commit into
dev
Choose a base branch
from
renovate/major-astro-monorepo
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
40f643f to
bfbcb6f
Compare
bfbcb6f to
82f2bc7
Compare
0cb0bed to
03a5d31
Compare
38f3f6f to
6511552
Compare
6511552 to
9b87490
Compare
c965677 to
f9764d6
Compare
f9764d6 to
1eb0115
Compare
1eb0115 to
6c1f9b0
Compare
6c1f9b0 to
a68cfd7
Compare
a68cfd7 to
1c1ce1e
Compare
1c1ce1e to
6503314
Compare
1194370 to
6150ab4
Compare
6150ab4 to
4791924
Compare
4791924 to
5be9356
Compare
c753044 to
bc17f29
Compare
bc17f29 to
9c25ce6
Compare
3dcece6 to
409b7f4
Compare
409b7f4 to
66a0234
Compare
7eb78df to
64317e6
Compare
64317e6 to
ac684e3
Compare
ac684e3 to
99d8903
Compare
99d8903 to
781f01f
Compare
781f01f to
838baaa
Compare
838baaa to
10ba36a
Compare
10ba36a to
a4ffd0b
Compare
90d4791 to
df36223
Compare
df36223 to
0478595
Compare
0478595 to
75fa3a4
Compare
73d15e5 to
434ec38
Compare
434ec38 to
001d295
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
5.7.3→7.2.45.1.5→6.0.2Release Notes
withastro/astro (@astrojs/svelte)
v7.2.4Compare Source
Patch Changes
16f3994Thanks @antonyfaris! - Fixes an issue where Svelte components used in Astro files would incorrectly report type errors when usingclient:*directives.v7.2.3Compare Source
Patch Changes
4264a36Thanks @antonyfaris! - Fixes an issue where Svelte 5 components used in Astro files would not have proper type checking and IntelliSense.v7.2.2Compare Source
Patch Changes
#14715
3d55c5dThanks @ascorbic! - Adds support for client hydration ingetContainerRenderer()The
getContainerRenderer()function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually callcontainer.addClientRenderer()with the appropriate client renderer entrypoint.See the
container-with-vitestdemo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.v7.2.1Compare Source
Patch Changes
e3175d9Thanks @GameRoMan! - Updatesviteversion to fix CVEv7.2.0Compare Source
Minor Changes
#14430
78011baThanks @ascorbic! - Adds support for async server renderingSvelte 5.36 added experimental support for async rendering. This allows you to use
awaitin your components in several new places. This worked out of the box with client-rendered components, but server-rendered components needed some extra help. This update adds support for async server rendering in Svelte components used in Astro.To use async rendering, you must enable it in your Svelte config:
Then you can use
awaitin your components:See the Svelte docs for more information on using
awaitin Svelte components, including inside$derivedblocks and directly in markup.Patch Changes
9cc8f21Thanks @ascorbic! - Fixes a bug that prevented Svelte 5.39.1+ components rendering when multiple frameworks were presentv7.1.1Compare Source
Patch Changes
c24a8f4Thanks @jsparkdev! - Updatesviteversion to fix CVEv7.1.0Compare Source
Minor Changes
#13809
3c3b492Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro's Node.js support policy for more details.
v7.0.13Compare Source
Patch Changes
c3e80c2Thanks @jsparkdev! - update vite to latest version for fixing CVEv7.0.12Compare Source
Patch Changes
e1cd1aeThanks @florian-lefebvre! - Fixes SSR renderer typev7.0.11Compare Source
Patch Changes
a19a185Thanks @florian-lefebvre! - Improves type-safety of renderersv7.0.10Compare Source
Patch Changes
#13596
3752519Thanks @jsparkdev! - update vite to latest version to fix CVE#13547
360cb91Thanks @jsparkdev! - Updates vite to the latest versionv7.0.9Compare Source
Patch Changes
ff9d69eThanks @jsparkdev! - updateviteto the latest versionv7.0.8Compare Source
Patch Changes
a98ae5bThanks @ematipico! - Updates the dependencyviteto the latest.v7.0.7Compare Source
Patch Changes
ecadb6bThanks @ascorbic! - Hides fallback content when renderingclient:onlyislandv7.0.6Compare Source
Patch Changes
a05e6abThanks @Hugos68! - Fixes a case where$props.id()would not be unique across multiple islandsv7.0.5Compare Source
Patch Changes
80926faThanks @ematipico! - Updatesesbuildandviteto the latest to avoid false positives audits warnings caused byesbuild.v7.0.4Compare Source
Patch Changes
cf30880Thanks @ascorbic! - Upgrades Vitev7.0.3Compare Source
Patch Changes
8809b85Thanks @aminevg! - Fixes an issue where TypeScript couldn't infer the correct types of theserver.mjsfilev7.0.2Compare Source
Patch Changes
739dbfbThanks @ascorbic! - Upgrades Vite to pin esbuildv7.0.1Compare Source
Patch Changes
c3e80c2Thanks @jsparkdev! - update vite to latest version for fixing CVEv7.0.0Compare Source
Major Changes
#12060
cb5d3aeThanks @Princesseuh! - Updates peer dependency range to support Astro 5#12524
9f44019Thanks @bluwy! - Updates@sveltejs/vite-plugin-svelteto v5 to handle Vite 6#12524
9f44019Thanks @bluwy! - Updates Vite dependency to v6 to match Astro v5Minor Changes
827093eThanks @bluwy! - Drops node 21 supportPatch Changes
#12102
dcc1e89Thanks @hermit99! - Fixes an Reference Error that occurred during client transitions#12551
b21a075Thanks @ematipico! - New release to include changes from 5.7.3v6.0.2Compare Source
Patch Changes
#12481
8a46e80Thanks @marbrex! - Resolvevitepeer dependency problem for strict package managers like Yarn in PnP mode.Updated dependencies [
c48916c,4364bff,c8f877c,8309c61,af867f3,3f02d5f]:v6.0.1Compare Source
Patch Changes
bde49f1Thanks @bluwy! - Publishes missing filev6.0.0Compare Source
Major Changes
#12364
9fc2ab8Thanks @jdtjenkins! - Adds support for Svelte 5. Svelte 3 and 4 are no longer supported.The integration will now also no longer add
vitePreprocess()by default if a preprocessor is not set up insvelte.config.js. It is recommended to set up the Svelte config manually so that features like IDE completion and syntax highlighting work properly.If you're using SCSS, Stylus, etc in your Svelte component style tags, make sure that the preprocessor is also set up in
svelte.config.js. For example:Refer to the Svelte 5 migration guide and
@sveltejs/vite-plugin-sveltechangelog for details of their respective breaking changes.withastro/astro (@astrojs/tailwind)
v6.0.2Compare Source
Patch Changes
a98ae5bThanks @ematipico! - Updates the dependencyviteto the latest.v6.0.1Compare Source
Patch Changes
020c542Thanks @delucis! - Updates the README to indicate that the Tailwind integration is deprecatedv6.0.0Compare Source
Major Changes
#13049
2ed4bd9Thanks @florian-lefebvre! - Deprecates the integrationTailwind CSS now offers a Vite plugin which is the preferred way to use Tailwind 4 in Astro. Please uninstall
@astrojs/tailwindand follow the Tailwind documentation for manual installation.This updated major version is only provided as a convenience for existing projects until they are able to migrate to the new plugin. It offers no additional functionality and is no longer recommended, but may continue to be used in your projects until it is removed entirely.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.