Skip to content

chore(deps): update astro monorepo (major) #1868

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.

Sign up for GitHub

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

Jump to bottom
Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update astro monorepo (major) #1868

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 3, 2024 •
edited
Loading

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@astrojs/react (source) ^1.2.2 || ^2.0.0 || ^3.0.0 → ^1.2.2 || ^2.0.0 || ^3.0.0 || ^4.0.0 age confidence
@astrojs/react (source) 3.6.3 → 4.4.2 age confidence
@astrojs/svelte (source) ^1.0.2 || ^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 → ^1.0.2 || ^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 age confidence
@astrojs/svelte (source) 6.0.2 → 7.2.5 age confidence
@astrojs/vue (source) ^1.2.2 || ^2.0.0 || ^3.0.0 || ^4.0.0 → ^1.2.2 || ^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.0 age confidence
@astrojs/vue (source) 4.5.3 → 5.1.4 age confidence
astro (source) ^3.0.0 || ^4.0.0 → ^3.0.0 || ^4.0.0 || ^5.0.0 age confidence
astro (source) 4.16.15 → 5.16.7 age confidence

Release Notes

withastro/astro (@​astrojs/react)

v4.4.2

Compare Source

Patch Changes

  • #​14715 3d55c5d Thanks @​ascorbic! - Adds support for client hydration in getContainerRenderer()

    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 call container.addClientRenderer() with the appropriate client renderer entrypoint.

    See the container-with-vitest demo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.

v4.4.1

Compare Source

Patch Changes

v4.4.0

Compare Source

Minor Changes

  • #​14386 f75f446 Thanks @​yanthomasdev! - Stabilizes the formerly experimental getActionState() and withState() functions introduced in @astrojs/react v3.4.0 used to integrate Astro Actions with React 19's useActionState() hook.

    This example calls a like action that accepts a postId and returns the number of likes. Pass this action to the withState() function to apply progressive enhancement info, and apply to useActionState() to track the result:

    import { actions } from 'astro:actions';
import { withState } from '@​astrojs/react/actions';
import { useActionState } from 'react';

export function Like({ postId }: { postId: string }) {
  const [state, action, pending] = useActionState(
    withState(actions.like),
    0, // initial likes
  );

  return (
    <form action={action}>
      <input type="hidden" name="postId" value={postId} />
      <button disabled={pending}>{state} ❤️</button>
    </form>
  );
}

    You can also access the state stored by useActionState() from your action handler. Call getActionState() with the API context, and optionally apply a type to the result:

    import { defineAction } from 'astro:actions';
import { z } from 'astro:schema';
import { getActionState } from '@&#8203;astrojs/react/actions';

export const server = {
  like: defineAction({
    input: z.object({
      postId: z.string(),
    }),
    handler: async ({ postId }, ctx) => {
      const currentLikes = getActionState<number>(ctx);
      // write to database
      return currentLikes + 1;
    },
  }),
};

    If you were previously using this experimental feature, you will need to update your code to use the new stable exports:

    // src/components/Form.jsx
import { actions } from 'astro:actions';
-import { experimental_withState } from '@&#8203;astrojs/react/actions';
+import { withState } from '@&#8203;astrojs/react/actions';
import { useActionState } from "react";
    // src/actions/index.ts
import { defineAction, type SafeResult } from 'astro:actions';
import { z } from 'astro:schema';
-import { experimental_getActionState } from '@&#8203;astrojs/react/actions';
+import { getActionState } from '@&#8203;astrojs/react/actions';

v4.3.1

Compare Source

Patch Changes

v4.3.0

Compare Source

Minor Changes

  • #​13809 3c3b492 Thanks @​ascorbic! - Increases minimum Node.js version to 18.20.8

    Node.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.

    ⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

v4.2.7

Compare Source

Patch Changes

v4.2.6

Compare Source

Patch Changes

v4.2.5

Compare Source

Patch Changes

v4.2.4

Compare Source

Patch Changes

v4.2.3

Compare Source

Patch Changes

v4.2.2

Compare Source

Patch Changes

v4.2.1

Compare Source

Patch Changes

v4.2.0

Compare Source

Minor Changes

  • #​13036 3c90d8f Thanks @​artmsilva! - Adds experimental support for disabling streaming

    This is useful to support libraries that are not compatible with streaming such as some CSS-in-JS libraries. To disable streaming for all React components in your project, set experimentalDisableStreaming: true as a configuration option for @astrojs/react:

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import react from '@&#8203;astrojs/react';

export default defineConfig({
  integrations: [
    react({
+      experimentalDisableStreaming: true,
    }),
  ],
});

v4.1.6

Compare Source

Patch Changes

  • #​12996 80c6801 Thanks @​bluwy! - Removes hardcoded ssr.external: ['react-dom/server', 'react-dom/client'] config that causes issues with adapters that bundle all dependencies (e.g. Cloudflare). These externals should already be inferred by default by Vite when deploying to a server environment.

  • #​13011 cf30880 Thanks @​ascorbic! - Upgrades Vite

v4.1.5

Compare Source

Patch Changes
  • #​12887 ea603ae Thanks @​louisescher! - Adds a warning message when multiple JSX-based UI frameworks are being used without either the include or exclude property being set on the integration.

v4.1.4

Compare Source

Patch Changes
  • #​12923 c7642fb Thanks @​bluwy! - Removes react-specific entrypoints in optimizeDeps.include and rely on @vitejs/plugin-react to add

v4.1.3

Compare Source

Patch Changes

v4.1.2

Compare Source

Patch Changes

v4.1.1

Compare Source

Patch Changes

v4.1.0

Compare Source

Minor Changes

v4.0.0

Compare Source

Major Changes
Minor Changes

  • #​12539 827093e Thanks @​bluwy! - Drops node 21 support

  • #​12510 14feaf3 Thanks @​bholmesdev! - Changes the generated URL query param from _astroAction to _action when submitting a form using Actions. This avoids leaking the framework name into the URL bar, which may be considered a security issue.

withastro/astro (@​astrojs/svelte)

v7.2.5

Compare Source

Patch Changes

v7.2.4

Compare Source

Patch Changes
  • #​15004 16f3994 Thanks @​antonyfaris! - Fixes an issue where Svelte components used in Astro files would incorrectly report type errors when using client:* directives.

v7.2.3

Compare Source

Patch Changes
  • #​14934 4264a36 Thanks @​antonyfaris! - Fixes an issue where Svelte 5 components used in Astro files would not have proper type checking and IntelliSense.

v7.2.2

Compare Source

Patch Changes

  • #​14715 3d55c5d Thanks @​ascorbic! - Adds support for client hydration in getContainerRenderer()

    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 call container.addClientRenderer() with the appropriate client renderer entrypoint.

    See the container-with-vitest demo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.

v7.2.1

Compare Source

Patch Changes

v7.2.0

Compare Source

Minor Changes

  • #​14430 78011ba Thanks @​ascorbic! - Adds support for async server rendering

    Svelte 5.36 added experimental support for async rendering. This allows you to use await in 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:

    // svelte.config.js
export default {
  compilerOptions: {
    experimental: {
      async: true,
    },
  },
};

    Then you can use await in your components:

    <script>
  let data = await fetch('/api/data').then(res => res.json());
</script>
<h1>{data.title}</h1>

    See the Svelte docs for more information on using await in Svelte components, including inside $derived blocks and directly in markup.

Patch Changes
  • #​14433 9cc8f21 Thanks @​ascorbic! - Fixes a bug that prevented Svelte 5.39.1+ components rendering when multiple frameworks were present

v7.1.1

Compare Source

Patch Changes

v7.1.0

Compare Source

Minor Changes

  • #​13809 3c3b492 Thanks @​ascorbic! - Increases minimum Node.js version to 18.20.8

    Node.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.

    ⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

v7.0.13

Compare Source

Patch Changes

v7.0.12

Compare Source

Patch Changes

v7.0.11

Compare Source

Patch Changes

v7.0.10

Compare Source

Patch Changes

v7.0.9

Compare Source

Patch Changes

v7.0.8

Compare Source

Patch Changes

v7.0.7

Compare Source

Patch Changes

v7.0.6

Compare Source

Patch Changes

v7.0.5

Compare Source

Patch Changes

v7.0.4

Compare Source

Patch Changes

v7.0.3

Compare Source

Patch Changes

v7.0.2

Compare Source

Patch Changes

v7.0.1

Compare Source

Patch Changes

v7.0.0

Compare Source

Major Changes
Minor Changes
Patch Changes
withastro/astro (@​astrojs/vue)

v5.1.4

Compare Source

Patch Changes

v5.1.3

Compare Source

Patch Changes

  • #​14715 3d55c5d Thanks @​ascorbic! - Adds support for client hydration in getContainerRenderer()

    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 call container.addClientRenderer() with the appropriate client renderer entrypoint.

    See the container-with-vitest demo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.

v5.1.2

Compare Source

Patch Changes

v5.1.1

Compare Source

Patch Changes

v5.1.0

Compare Source

Minor Changes

  • #​13809 3c3b492 Thanks @​ascorbic! - Increases minimum Node.js version to 18.20.8

    Node.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.

    ⚠️ Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.

v5.0.13

Compare Source

Patch Changes

v5.0.12

Compare Source

Patch Changes

v5.0.11

Compare Source

Patch Changes

v5.0.10

Compare Source

Patch Changes

v5.0.9

Compare Source

Patch Changes

v5.0.8

Compare Source

Patch Changes

v5.0.7

Compare Source

Patch Changes

v5.0.6

Compare Source

Patch Changes

v5.0.5

Compare Source

Patch Changes
  • #​12887 ea603ae Thanks @​louisescher! - Adds a warning message when multiple JSX-based UI frameworks are being used without either the include or exclude property being set on the integration.

v5.0.4

Compare Source

Patch Changes

v5.0.3

Compare Source

Patch Changes

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes

v5.0.0

Compare Source

Major Changes
Minor Changes
Patch Changes
withastro/astro (astro)

v5.16.7

Compare Source

Patch Changes

  • #​15122 b137946 Thanks @​florian-lefebvre! - Improves JSDoc annotations for AstroGlobal, AstroSharedContext and APIContext types

  • #​15123 3f58fa2 Thanks @​43081j! - Improves rendering performance by grouping render chunks when emitting from async iterables to avoid encoding costs

  • #​14954 7bec4bd Thanks @​volpeon! - Fixes remote images Etag header handling by disabling internal cache

  • #​15052 b2bcd5a Thanks @​Princesseuh! - Fixes images not working in development when using setups with port forwarding

  • #​15028 87b19b8 Thanks @​Princesseuh! - Fixes certain aliases not working when using images in JSON files with the content layer

  • #​15118 cfa382b Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

    Removes the defineAstroFontProvider() type helper.

    If you are building a custom font provider, remove any occurrence of defineAstroFontProvider() and use the FontProvider type instead:

    -import { defineAstroFontProvider } from 'astro/config';

-export function myProvider() {
-    return defineAstroFontProvider({
-        entrypoint: new URL('./implementation.js', import.meta.url)
-    });
-};

+import type { FontProvider } from 'astro';

+export function myProvider(): FontProvider {
+    return {
+        entrypoint: new URL('./implementation.js', import.meta.url)
+    },
+}

  • #​15055 4e28db8 Thanks @​delucis! - Reduces Astro’s install size by around 8 MB

  • #​15088 a19140f Thanks @​martrapp! - Enables the ClientRouter to preserve the original hash part of the target URL during server side redirects.

  • #​15117 b1e8e32 Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

    Changes the font format downloaded by default when using the experimental Fonts API. Additionally, adds a new formats configuration option to specify which font formats to download.

    Previously, Astro was opinionated about which font sources would be kept for usage, mainly keeping woff2 and woff files.

    You can now specify what font formats should be downloaded (if available). Only woff2 files are downloaded by default.

What should I do?

If you were previously relying on Astro downloading the woff format, you will now need to specify this explicitly with the new formats configuration option.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch 4 times, most recently from 0c7ec07 to cbe7444 Compare December 10, 2024 07:15
@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 3d556cc to c970fb0 Compare December 17, 2024 06:16
@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch 11 times, most recently from a485c98 to a3bcdc3 Compare December 23, 2024 02:26
@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from 959a819 to 43d3838 Compare January 2, 2025 14:01
@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch 5 times, most recently from bea5c2d to 9e1c866 Compare January 13, 2025 15:47
@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch 5 times, most recently from dfa9748 to e7088f9 Compare January 20, 2025 09:19
@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from da9bda8 to 4a2c6a9 Compare September 26, 2025 15:38
@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from c407339 to 6cad399 Compare October 14, 2025 17:50
@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch 5 times, most recently from ee7ee7b to cdf422f Compare October 23, 2025 15:12
@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from d9f27f7 to 4843fb7 Compare October 30, 2025 18:57
@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 503af40 to a543f23 Compare November 13, 2025 17:13
@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch 5 times, most recently from 77bfd68 to 1037b03 Compare November 20, 2025 14:59
@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 0c378a5 to 8e06f4f Compare November 29, 2025 20:54
@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from ddfaf94 to 7ad7fb3 Compare December 3, 2025 20:11
@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch from 7ad7fb3 to 176ccb6 Compare December 10, 2025 17:27
@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch from 176ccb6 to b23c6c4 Compare December 18, 2025 16:03
@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch from b23c6c4 to c2359bc Compare December 31, 2025 18:39
@renovate renovate bot force-pushed the renovate/major-astro-monorepo branch from c2359bc to 992b3d8 Compare January 7, 2026 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant