Skip to content

Update astro monorepo (major)#51

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-astro-monorepo
Open

Update astro monorepo (major)#51
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-astro-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Jan 30, 2025 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@astrojs/mdx (source) 4.0.3 → 6.0.1 age confidence
@astrojs/react (source) 4.1.2 → 5.0.6 age confidence
@astrojs/tailwind (source) 5.1.4 → 6.0.2 age confidence
astro (source) 5.1.1 → 6.4.2 age confidence

Release Notes

withastro/astro (@​astrojs/mdx)

v6.0.1

Patch Changes

v6.0.0

Compare Source

Major Changes

  • #​16848 f732f3c Thanks @​Princesseuh! - Adds a new markdown.processor configuration option, allowing you to choose an alternative Markdown processor.

    Websites with many Markdown/MDX files tend to be slow to build because the unified ecosystem (e.g., remark, rehype) is slow to process. This feature introduces the ability to replace this part of the build pipeline with another processor.

    The default processor is unified(). This means that existing configurations remain unchanged and your remark/rehype plugins continue to work.

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import { unified } from '@​astrojs/markdown-remark';
import remarkToc from 'remark-toc';

export default defineConfig({
  markdown: {
    processor: unified({
      remarkPlugins: [remarkToc],
    }),
  },
});

    In addition to this new configuration option, Astro provides a new alternative processor based on Rust: Sätteri. You can choose to use it now by installing @astrojs/markdown-satteri, importing the satteri() processor, and adapting your existing configuration:

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import { satteri } from '@​astrojs/markdown-satteri';

export default defineConfig({
  markdown: {
    processor: satteri({
      features: { directive: true },
    }),
  },
});

    This processor does not support the remark and rehype plugins. This means you may need to convert them to MDAST or HAST plugins to retain your current functionality.

    The existing top-level markdown.remarkPlugins, markdown.rehypePlugins, markdown.remarkRehype, markdown.gfm, and markdown.smartypants options still work, but are now deprecated and will be removed in a future major update. The matching remarkPlugins, rehypePlugins, and remarkRehype options on the MDX integration are also deprecated for the same reason. To anticipate their removal, move them onto unified({...}) (or your preferred plugin processor) :

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import remarkToc from 'remark-toc';
import rehypeSlug from 'rehype-slug';
+ import { unified } from '@​astrojs/markdown-remark';

export default defineConfig({
  markdown: {
+    processor: unified({
+      remarkPlugins: [remarkToc],
+      rehypePlugins: [rehypeSlug],
+      remarkRehype: true,
+      gfm: true,
+      smartypants: true,
+    }),
-    remarkPlugins: [remarkToc],
-    rehypePlugins: [rehypeSlug],
-    remarkRehype: true,
-    gfm: true,
-    smartypants: true,
  },
});

    For more information on enabling and using this feature in your project, see our Markdown guide. To give feedback on this new Rust processor, see the Native Markdown / MDX parsing and processing RFC.

Minor Changes

  • #​16848 f732f3c Thanks @​Princesseuh! - Adds support for using @astrojs/markdown-satteri to parse .mdx files.

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import mdx from '@​astrojs/mdx';
import { satteri } from '@​astrojs/markdown-satteri';

export default defineConfig({
  markdown: {
    processor: satteri({
      features: { directive: true },
    }),
  },
  integrations: [mdx()],
});

    Note that the recmaPlugins option is not supported when using Sätteri as your MDX processor. If you would like to use Sätteri for Markdown files, but still use Unified for MDX, you can pass a different Markdown processor to the MDX integration:

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import mdx from '@​astrojs/mdx';
import { satteri } from '@​astrojs/markdown-satteri';
import { unified } from '@​astrojs/markdown-remark';
import myPlugin from './my-recma-plugin.js';

export default defineConfig({
  markdown: {
    processor: satteri({
      features: { directive: true },
    }),
  },
  integrations: [
    mdx({
      recmaPlugins: [myPlugin],
      processor: unified(),
    }),
  ],
});
Patch Changes

v5.0.6

Compare Source

Patch Changes

v5.0.5

Compare Source

Patch Changes

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
Patch Changes

v4.3.14

Compare Source

Patch Changes

v4.3.13

Compare Source

Patch Changes

v4.3.12

Compare Source

Patch Changes

v4.3.11

Compare Source

Patch Changes

v4.3.10

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

Patch Changes

v4.3.8

Patch Changes

  • #​14591 3e887ec Thanks @​matthewp! - Adds TypeScript support for the components prop on MDX Content component when using await render(). Developers now get proper IntelliSense and type checking when passing custom components to override default MDX element rendering.

  • #​14598 7b45c65 Thanks @​delucis! - Reduces terminal text styling dependency size by switching from kleur to picocolors

v4.3.7

Compare Source

Patch Changes

v4.3.6

Compare Source

Patch Changes

v4.3.5

Compare Source

Patch Changes

v4.3.4

Compare Source

Patch Changes

v4.3.3

Compare Source

Patch Changes

v4.3.2

Compare Source

Patch Changes

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.

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

Patch Changes

v4.2.1

Patch Changes

v4.2.0

Compare Source

Minor Changes

  • #​13352 cb886dc Thanks @​delucis! - Adds support for a new experimental.headingIdCompat flag

    By default, Astro removes a trailing - from the end of IDs it generates for headings ending with
    special characters. This differs from the behavior of common Markdown processors.

    You can now disable this behavior with a new configuration flag:

    // astro.config.mjs
import { defineConfig } from 'astro/config';

export default defineConfig({
  experimental: {
    headingIdCompat: true,
  },
});

    This can be useful when heading IDs and anchor links need to behave consistently across your site
    and other platforms such as GitHub and npm.

    If you are using the rehypeHeadingIds plugin directly, you can also pass this new option:

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import { rehypeHeadingIds } from '@​astrojs/markdown-remark';
import { otherPluginThatReliesOnHeadingIDs } from 'some/plugin/source';

export default defineConfig({
  markdown: {
    rehypePlugins: [
      [rehypeHeadingIds, { experimentalHeadingIdCompat: true }],
      otherPluginThatReliesOnHeadingIDs,
    ],
  },
});
Patch Changes

v4.1.1

Compare Source

Patch Changes

v4.1.0

Compare Source

Minor Changes

  • #​13254 1e11f5e Thanks @​p0lyw0lf! - Adds the ability to process and optimize remote images in Markdown syntax in MDX files.

    Previously, Astro only allowed local images to be optimized when included using ![]() syntax. Astro's image service could only display remote images without any processing.

    Now, Astro's image service can also optimize remote images written in standard Markdown syntax. This allows you to enjoy the benefits of Astro's image processing when your images are stored externally, for example in a CMS or digital asset manager.

    No additional configuration is required to use this feature! Any existing remote images written in Markdown will now automatically be optimized. To opt-out of this processing, write your images in Markdown using the JSX <img/> tag instead. Note that images located in your public/ folder are still never processed.

Patch Changes

v4.0.8

Compare Source

Patch Changes

v4.0.7

Compare Source

Patch Changes

v4.0.6

Compare Source

Patch Changes

v4.0.5

Compare Source

Patch Changes

v4.0.4

Compare Source

Patch Changes

  • #​12921 aeb7e1a Thanks @​ascorbic! - Fixes a bug that caused Image component to be imported on MDX pages that did not include images

  • #​12913 9a3b48c Thanks @​bluwy! - Makes internal check() function a no-op to allow faster component renders and prevent React 19 component warnings

withastro/astro (@​astrojs/react)

v5.0.6

Compare Source

Patch Changes

v5.0.5

Compare Source

Patch Changes

v5.0.4

Compare Source

Patch Changes

v5.0.3

Compare Source

Patch Changes
  • #​16224 a2b9eeb Thanks @​fkatsuhiro! - Fix React 19 "Float" mechanism injecting into Astro islands instead of the . This PR adds a filter to @​astrojs/react to strip these auto-generated resource from the island's HTML output, ensuring valid HTML structure.

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

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 '@&#8203;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 Ch

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

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

  • 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 2 times, most recently from 94145fd to eff835e Compare March 26, 2025 12:47
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from 7f61960 to 0d98cb1 Compare August 13, 2025 17:26
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch from 0d98cb1 to 10b9b97 Compare August 19, 2025 15:37
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch from 10b9b97 to ef6059c Compare August 31, 2025 11:29
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch from ef6059c to 3027f10 Compare September 25, 2025 21:30
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch from 3027f10 to ec79252 Compare October 21, 2025 22:07
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch from ec79252 to 143f4bf Compare November 10, 2025 15:13
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch from 143f4bf to cbb209b Compare November 18, 2025 22:47
@renovate renovate Bot changed the title fix(deps): update dependency @astrojs/tailwind to v6 Update dependency @astrojs/tailwind to v6 Nov 29, 2025
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch from cbb209b to bdf8c7d Compare December 3, 2025 17:31
@renovate renovate Bot changed the title Update dependency @astrojs/tailwind to v6 fix(deps): update dependency @astrojs/tailwind to v6 Dec 28, 2025
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch from bdf8c7d to 4564f74 Compare December 28, 2025 19:27
@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages Bot commented Dec 28, 2025 •
edited
Loading

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
❌ Deployment failed
View logs		 raphael-arce-de 2a90467 Dec 31 2025, 04:46 PM

@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from 52389b4 to 2a90467 Compare December 31, 2025 16:45
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch from 2a90467 to 23758dd Compare January 8, 2026 17:39
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from c561e39 to e271ddb Compare January 23, 2026 19:49
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch from e271ddb to c27948a Compare February 2, 2026 19:11
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from f5f451b to 9e33732 Compare February 17, 2026 16:40
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from ee9bd64 to 7e2bba9 Compare March 10, 2026 14:54
@renovate renovate Bot changed the title fix(deps): update dependency @astrojs/tailwind to v6 fix(deps): update astro monorepo (major) Mar 10, 2026
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Mar 10, 2026 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: raphael.arce.de@0.0.1
npm error Found: astro@6.4.2
npm error node_modules/astro
npm error   astro@"6.4.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer astro@"^3.0.0 || ^4.0.0 || ^5.0.0" from @astrojs/tailwind@6.0.2
npm error node_modules/@astrojs/tailwind
npm error   @astrojs/tailwind@"6.0.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-05-28T16_30_22_451Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-05-28T16_30_22_451Z-debug-0.log

@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 615c8bc to 6ba8b64 Compare March 11, 2026 21:30
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 69665bc to c8d11a0 Compare March 18, 2026 17:44
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 4 times, most recently from 16645bf to 46c190d Compare March 26, 2026 20:44
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from 91a5398 to 1033ee4 Compare April 1, 2026 22:08
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from 925c9d9 to 56ca44c Compare April 8, 2026 21:35
@renovate renovate Bot changed the title fix(deps): update astro monorepo (major) Update astro monorepo (major) Apr 8, 2026
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 78c10e0 to 9950d68 Compare April 18, 2026 12:39
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from 93176f1 to 0daa4b6 Compare April 28, 2026 17:28
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 4 times, most recently from 4bc094e to 0e83df2 Compare May 7, 2026 10:08
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 7f522a7 to 07e9479 Compare May 14, 2026 18:43
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 0f5a632 to 13ec65b Compare May 21, 2026 17:48
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch from 13ec65b to 2c97948 Compare May 26, 2026 22:15
@renovate renovate Bot force-pushed the renovate/major-astro-monorepo branch from 2c97948 to ab1265a Compare May 28, 2026 16:30
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.

0 participants