Update astro monorepo (major) by renovate[bot] · Pull Request #51 · raphael-arce/raphael-arce.github.io

renovate · 2025-01-30T13:16:22Z

ℹ️ 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` → `8.0.1`
@astrojs/react (source)	`4.1.2` → `6.0.5`
@astrojs/tailwind (source)	`5.1.4` → `6.0.2`
astro (source)	`5.1.1` → `7.3.2`

Release Notes

withastro/astro (@astrojs/mdx)

Major Changes

#17262 f8e9458 Thanks @Princesseuh! - Moves MDX file processing to the Markdown processors.

'@astrojs/mdx' is still required to add MDX support to your project. However, it now delegates the MDX files processing to Markdown processors.

What should I do?

If you haven't explicitly installed a Markdown processor, you don't need to do anything.

Otherwise, ensure that your configured Markdown processor uses the following version:

@astrojs/markdown-satteri 0.4.0 or later if you use satteri()
@astrojs/markdown-remark 7.3.0 or later if you use unified()

Patch Changes

#17262 f8e9458 Thanks @Princesseuh! - Fixes .mdx files still using markdown.processor when extendMarkdownConfig is false. They now use a clean default processor instead; pass mdx({ processor }) to choose one explicitly.
#17262 f8e9458 Thanks @Princesseuh! - Adds a warning when the deprecated remarkPlugins, rehypePlugins, recmaPlugins and remarkRehype options are ignored because your Markdown processor does not run them. They still apply when your processor is unified(), and were previously dropped silently otherwise.
Updated dependencies [f8e9458, f8e9458]:
- @astrojs/internal-helpers@0.11.0
- @astrojs/markdown-satteri@0.4.0

`v7.0.8`

Compare Source

Patch Changes

#17757 660991c Thanks @astro-factory! - Fixes build errors showing wrong file location, missing line:col, and misleading hints when a plugin error (e.g. from MDX) is wrapped by Vite's build error
#17766 0762a83 Thanks @HiDeoo! - Fixes Sätteri processor option types to accept all plugin entries supported by Sätteri v0.10.3.

`v7.0.7`

Compare Source

Patch Changes

#17731 bc171af Thanks @Princesseuh! - Updates Sätteri processor to v0.10.3. See its changelog for details on bugs fixed and features added.
Updated dependencies [05763a0]:
- @astrojs/internal-helpers@0.10.4
- @astrojs/markdown-remark@7.2.4

`v7.0.6`

Compare Source

Patch Changes

Updated dependencies [8c193f6]:
- @astrojs/internal-helpers@0.10.3
- @astrojs/markdown-remark@7.2.3

`v7.0.5`

Compare Source

Patch Changes

Updated dependencies [c895b12]:
- @astrojs/internal-helpers@0.10.2
- @astrojs/markdown-remark@7.2.2

`v7.0.4`

Compare Source

Patch Changes

#17514 41a00dd Thanks @gtritchie! - Fixes a bug where the integration was emitting React-cased attribute names.

`v7.0.3`

Compare Source

Patch Changes

#17341 64b0d66 Thanks @Princesseuh! - Fixes custom pre components not applying to syntax-highlighted code blocks when using the Sätteri Markdown processor with MDX.

`v7.0.2`

Compare Source

Patch Changes

Updated dependencies [eb6f97e]:
- @astrojs/internal-helpers@0.10.1
- @astrojs/markdown-remark@7.2.1

`v7.0.1`

Compare Source

Patch Changes

#17249 02b73b0 Thanks @ematipico! - Fixes an issue where the peerDependencies field used incorrect dependencies.

`v7.0.0`

Compare Source

Major Changes

#15819 cafec4e Thanks @delucis! - Upgrade to Vite v8

Minor Changes

#17093 4585fe5 Thanks @Princesseuh! - Replaces the import entrypoint of getContainerRenderer()

A new container-renderer entrypoint exporting getContainerRenderer() has been added to the following integrations: React, Preact, Svelte, SolidJS, Vue, and MDX. This prevents bundlers from trying to bundle unrelated exports from the package root when only the Container API is used.

If you are using the Container API, update your import statements to use the new entrypoint. The following example updates the getContainerRenderer() import for React:
```
- import { getContainerRenderer } from '@astrojs/react';
+ import { getContainerRenderer } from '@astrojs/react/container-renderer';
```
Importing getContainerRenderer() from the package root still works, but is now deprecated and logs a warning.
#17129 ff7b718 Thanks @Princesseuh! - Adds support for modifying frontmatter programmatically with the default Markdown processor.

A Sätteri plugin can now read and mutate ctx.data.astro.frontmatter, and Astro uses the result as the page's frontmatter, in both Markdown and MDX.

Patch Changes

#17124 7e7ab87 Thanks @Princesseuh! - Updates satteri to 0.9.0. See the Sätteri changelog for details.
#17027 241250b Thanks @ocavue! - Triggers beta prereleases for packages that are still on alpha

`v6.0.3`

Compare Source

Patch Changes

#16969 4a31f90 Thanks @Princesseuh! - Adds support for Prism syntax highlighting to the Sätteri Markdown and MDX processors. Setting markdown.syntaxHighlight to 'prism' now highlights your code blocks with Prism.

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

export default defineConfig({
  markdown: {
    processor: satteri(),
    syntaxHighlight: 'prism',
  },
});

`v6.0.2`

Patch Changes

#16955 9a93d68 Thanks @Princesseuh! - Updates Sätteri processor to v0.8.0. See its changelog for details on bugs fixed and features added.
Updated dependencies [9a93d68]:
- @astrojs/markdown-satteri@0.2.2

`v6.0.1`

Patch Changes

Updated dependencies [eeb064c]:
- @astrojs/markdown-satteri@0.2.1

`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

Updated dependencies [f732f3c, f732f3c, f732f3c]:
- @astrojs/internal-helpers@0.10.0
- @astrojs/markdown-remark@7.2.0
- @astrojs/markdown-satteri@0.2.0

`v5.0.6`

Compare Source

Patch Changes

#16579 49e10e3 Thanks @igor-koop! - Fixes an issue where the smartypants option was ignored.

`v5.0.5`

Compare Source

Patch Changes

Updated dependencies [9256345]:
- @astrojs/markdown-remark@7.1.2

`v5.0.4`

Compare Source

Patch Changes

Updated dependencies [f3485c3]:
- @astrojs/markdown-remark@7.1.1

`v5.0.3`

Compare Source

Patch Changes

Updated dependencies [10a1a5a]:
- @astrojs/markdown-remark@7.1.0

`v5.0.2`

Compare Source

Patch Changes

#15864 d3c7de9 Thanks @florian-lefebvre! - Removes temporary support for Node >=20.19.1 because Stackblitz now uses Node 22 by default
Updated dependencies []:
- @astrojs/markdown-remark@7.0.1

`v5.0.1`

Compare Source

Patch Changes

#15934 6f8f0bc Thanks @ematipico! - Updates the Astro peerDependencies#astro to be 6.0.0.

`v5.0.0`

Compare Source

Major Changes

#14494 727b0a2 Thanks @florian-lefebvre! - Updates Markdown heading ID generation - (v6 upgrade guidance)
#14427 e131261 Thanks @florian-lefebvre! - Increases minimum Node.js version to 22.12.0 - (v6 upgrade guidance)
#14445 ecb0b98 Thanks @florian-lefebvre! - Astro v6.0 upgrades to Vite v7.0 as the development server and production bundler - (v6 upgrade guidance)

Patch Changes

#15187 bbb5811 Thanks @matthewp! - Update to Astro 6 beta
#15475 36fc0e0 Thanks @delucis! - Fixes edge cases where an export const components = {...} declaration would fail to be detected with the optimize option enabled
#15264 11efb05 Thanks @florian-lefebvre! - Lower the Node version requirement to allow running on Stackblitz until it supports v22
Updated dependencies [bbb5811, cb99214, 80f0225, 727b0a2, 1fa4177, 7c55f80, 6f19ecc, f94d3c5]:
- @astrojs/markdown-remark@7.0.0

`v4.3.14`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.11

`v4.3.13`

Compare Source

Patch Changes

Updated dependencies [d8305f8]:
- @astrojs/markdown-remark@6.3.10

`v4.3.12`

Compare Source

Patch Changes

#14813 e1dd377 Thanks @ematipico! - Removes picocolors as dependency in favor of the fork piccolore.

`v4.3.11`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.9

`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

#14621 e3175d9 Thanks @GameRoMan! - Updates vite version to fix CVE

`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

Updated dependencies []:
- @astrojs/markdown-remark@6.3.8

`v4.3.6`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.7

`v4.3.5`

Compare Source

Patch Changes

#14326 c24a8f4 Thanks @jsparkdev! - Updates vite version to fix CVE

`v4.3.4`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.6

`v4.3.3`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.5

`v4.3.2`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.3.4

`v4.3.1`

Compare Source

Patch Changes

Updated dependencies [6bd5f75]:
- @astrojs/markdown-remark@6.3.3

`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

Updated dependencies []:
- @astrojs/markdown-remark@6.3.2

`v4.2.6`

Compare Source

Patch Changes

#13731 c3e80c2 Thanks @jsparkdev! - update vite to latest version for fixing CVE

`v4.2.5`

Compare Source

Patch Changes

#13591 5dd2d3f Thanks @florian-lefebvre! - Removes unused code

`v4.2.4`

Compare Source

Patch Changes

#13596 3752519 Thanks @jsparkdev! - update vite to latest version to fix CVE
#13547 360cb91 Thanks @jsparkdev! - Updates vite to the latest version

`v4.2.3`

Compare Source

Patch Changes

#13526 ff9d69e Thanks @jsparkdev! - update vite to the latest version

`v4.2.2`

Patch Changes

#13505 a98ae5b Thanks @ematipico! - Updates the dependency vite to the latest.

`v4.2.1`

Patch Changes

#13448 91c9503 Thanks @ematipico! - Upgrade to shiki v3
Updated dependencies [91c9503]:
- @astrojs/markdown-remark@6.3.1

`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

Updated dependencies [cb886dc, a3327ff]:
- @astrojs/markdown-remark@6.3.0

`v4.1.1`

Compare Source

Patch Changes

Updated dependencies []:
- @astrojs/markdown-remark@6.2.1

`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

Updated dependencies [1e11f5e]:
- @astrojs/markdown-remark@6.2.0

`v4.0.8`

Compare Source

Patch Changes

Updated dependencies [db252e0]:
- @astrojs/markdown-remark@6.1.0

`v4.0.7`

Compare Source

Patch Changes

#13011 cf30880 Thanks @ascorbic! - Upgrades Vite

`v4.0.6`

Compare Source

Patch Changes

Updated dependencies [3d89e62]:
- @astrojs/markdown-remark@6.0.2

`v4.0.5`

Compare Source

Patch Changes

#12959 3a267f3 Thanks @bluwy! - Reverts 9a3b48c which caused a regression for rendering inline MDX components and MDX files from content collections

`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)

`v6.0.5`

Compare Source

Patch Changes

Updated dependencies [f8e9458]:
- @astrojs/internal-helpers@0.11.0

`v6.0.4`

Compare Source

Patch Changes

Updated dependencies [05763a0]:
- @astrojs/internal-helpers@0.10.4

`v6.0.3`

Compare Source

Patch Changes

Updated dependencies [8c193f6]:
- @astrojs/internal-helpers@0.10.3

`v6.0.2`

Compare Source

Patch Changes

Updated dependencies [c895b12]:
- @astrojs/internal-helpers@0.10.2

`v6.0.1`

Compare Source

Patch Changes

Updated dependencies [eb6f97e]:
- @astrojs/internal-helpers@0.10.1

`v6.0.0`

Compare Source

Major Changes

#15819 cafec4e Thanks @delucis! - Upgrade to Vite v8

Minor Changes

#17093 4585fe5 Thanks @Princesseuh! - Replaces the import entrypoint of getContainerRenderer()

A new container-renderer entrypoint exporting getContainerRenderer() has been added to the following integrations: React, Preact, Svelte, SolidJS, Vue, and MDX. This prevents bundlers from trying to bundle unrelated exports from the package root when only the Container API is used.

If you are using the Container API, update your import statements to use the new entrypoint. The following example updates the getContainerRenderer() import for React:
```
- import { getContainerRenderer } from '@astrojs/react';
+ import { getContainerRenderer } from '@astrojs/react/container-renderer';
```
Importing getContainerRenderer() from the package root still works, but is now deprecated and logs a warning.

Patch Changes

#17027 241250b Thanks @ocavue! - Triggers beta prereleases for packages that are still on alpha

`v5.0.7`

Compare Source

Patch Changes

#16900 17a0fbd Thanks @ocavue! - Bumps devalue dependency to v5.8.1

`v5.0.6`

Compare Source

Patch Changes

Updated dependencies [f732f3c]:
- @astrojs/internal-helpers@0.10.0

`v5.0.5`

Compare Source

Patch Changes

Updated dependencies [d365c97]:
- @astrojs/internal-helpers@0.9.1

`v5.0.4`

Compare Source

Patch Changes

Updated dependencies [99464ed, f3485c3]:
- @astrojs/internal-helpers@0.9.0

`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

#15378 a8a926e Thanks @dmgawel! - Fix React hydration errors when using conditional slot rendering
#15146 f771f75 Thanks @kedarvartak! - Fixes hydration mismatch when using experimentalReactChildren
#14917 769265b Thanks @sanjaiyan-dev! - Refactors to improve the performance of rendering static HTML content in React

`v5.0.1`

Compare Source

Patch Changes

#15864 d3c7de9 Thanks @florian-lefebvre! - Removes temporary support for Node >=20.19.1 because Stackblitz now uses Node 22 by default

[`v5.0.0`](https://redirect.github.com/withastro/astro/blob/HEAD

❗ Important

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

cloudflare-workers-and-pages · 2025-12-28T19:27:51Z

Deploying with 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 · 2026-03-10T14:54:23Z

⚠️ 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@7.3.2
npm error node_modules/astro
npm error   astro@"7.3.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-09-10T20_08_03_298Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-10T20_08_03_298Z-debug-0.log

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 Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from 7f61960 to 0d98cb1 Compare August 13, 2025 17:26

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 0d98cb1 to 10b9b97 Compare August 19, 2025 15:37

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 10b9b97 to ef6059c Compare August 31, 2025 11:29

renovate Bot force-pushed the renovate/major-astro-monorepo branch from ef6059c to 3027f10 Compare September 25, 2025 21:30

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 3027f10 to ec79252 Compare October 21, 2025 22:07

renovate Bot force-pushed the renovate/major-astro-monorepo branch from ec79252 to 143f4bf Compare November 10, 2025 15:13

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 143f4bf to cbb209b Compare November 18, 2025 22:47

renovate Bot changed the title ~~fix(deps): update dependency @astrojs/tailwind to v6~~ Update dependency @astrojs/tailwind to v6 Nov 29, 2025

renovate Bot force-pushed the renovate/major-astro-monorepo branch from cbb209b to bdf8c7d Compare December 3, 2025 17:31

renovate Bot changed the title ~~Update dependency @astrojs/tailwind to v6~~ fix(deps): update dependency @astrojs/tailwind to v6 Dec 28, 2025

renovate Bot force-pushed the renovate/major-astro-monorepo branch from bdf8c7d to 4564f74 Compare December 28, 2025 19:27

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 Bot force-pushed the renovate/major-astro-monorepo branch from 2a90467 to 23758dd Compare January 8, 2026 17:39

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 Bot force-pushed the renovate/major-astro-monorepo branch from e271ddb to c27948a Compare February 2, 2026 19:11

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 Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from ee9bd64 to 7e2bba9 Compare March 10, 2026 14:54

renovate Bot changed the title ~~fix(deps): update dependency @astrojs/tailwind to v6~~ fix(deps): update astro monorepo (major) Mar 10, 2026

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 Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 9950d68 to 93176f1 Compare April 22, 2026 18:33

renovate Bot force-pushed the renovate/major-astro-monorepo branch 4 times, most recently from 0003ed0 to 4bc094e Compare May 4, 2026 14:47

renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from c8af83f to 7f522a7 Compare May 13, 2026 21:12

renovate Bot force-pushed the renovate/major-astro-monorepo branch 4 times, most recently from 0f5a632 to 13ec65b Compare May 21, 2026 17:48

renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from 2c97948 to ab1265a Compare May 28, 2026 16:30

renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from c166892 to 016d4e5 Compare June 10, 2026 18:08

renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 0f4d03c to c8825c7 Compare June 22, 2026 10:35

renovate Bot force-pushed the renovate/major-astro-monorepo branch 4 times, most recently from 7ebd12c to dfd00ef Compare June 30, 2026 14:51

renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 9115fe4 to 7d681f5 Compare July 8, 2026 17:43

Update astro monorepo

32afe66

Navigation Menu

Update astro monorepo (major) - #51

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

renovate Bot commented Jan 30, 2025 •

edited

Loading

Uh oh!

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

edited

Loading

Uh oh!

renovate Bot commented Mar 10, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Jan 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Major Changes

What should I do?

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

renovate Bot commented Jan 30, 2025 •

edited

Loading

[`v5.0.0`](https://redirect.github.com/withastro/astro/blob/HEAD