Update astro monorepo (major) by renovate[bot] · Pull Request #103 · noahflk/noahflk.com

renovate · 2024-12-02T00:04:27Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/mdx (source)	`^3.0.0` → `^7.0.0`
@astrojs/svelte (source)	`^5.0.0` → `^9.0.0`
@astrojs/tailwind (source)	`^5.0.0` → `^6.0.0`
astro (source)	`4.16.19` → `7.0.7`

Release Notes

withastro/astro (@astrojs/mdx)

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 '@&#8203;astrojs/react';
+ import { getContainerRenderer } from '@&#8203;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 '@&#8203;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 '@&#8203;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 '@&#8203;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 '@&#8203;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 '@&#8203;astrojs/mdx';
import { satteri } from '@&#8203;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 '@&#8203;astrojs/mdx';
import { satteri } from '@&#8203;astrojs/markdown-satteri';
import { unified } from '@&#8203;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 '@&#8203;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

`v4.0.3`

Compare Source

Patch Changes

#12799 739dbfb Thanks @ascorbic! - Upgrades Vite to pin esbuild

`v4.0.2`

Compare Source

Patch Changes

Updated dependencies [f13417b, 87231b1, a71e9b9]:
- @astrojs/markdown-remark@6.0.1

`v4.0.1`

Compare Source

Patch Changes

#12594 4f2fd0a Thanks @Princesseuh! - Fixes compatibility with Astro 5

`v4.0.0`

Compare Source

Major Changes

#12231 90ae100 Thanks @bluwy! - Handles the breaking change in Astro where content pages (including .mdx pages located within src/pages/) no longer respond with charset=utf-8 in the Content-Type header.

For MDX pages without layouts, @astrojs/mdx will automatically add the <meta charset="utf-8"> tag to the page by default. This reduces the boilerplate needed to write with non-ASCII characters. If your MDX pages have a layout, the layout component should include the <meta charset="utf-8"> tag.

If you require charset=utf-8 to render your page correctly, make sure that your layout components have the <meta charset="utf-8"> tag added.
#12008 5608338 Thanks @Princesseuh! - Welcome to the Astro 5 beta! This release has no changes from the latest alpha of this package, but it does bring us one step closer to the final, stable release.

Starting from this release, no breaking changes will be introduced unless absolutely necessary.

To learn how to upgrade, check out the Astro v5.0 upgrade guide in our beta docs site.

Minor Changes

#12539 827093e Thanks @bluwy! - Drops node 21 support
#11741 6617491 Thanks @bluwy! - Updates adapter server entrypoint to use @astrojs/mdx/server.js

This is an internal change. Handling JSX in your .mdx files has been moved from Astro internals and is now the responsibility of this integration. You should not notice a change in your project, and no update to your code is required.

Patch Changes

#12075 a19530e Thanks @bluwy! - Parses frontmatter ourselves
#11861 3ab3b4e Thanks @bluwy! - Updates @astrojs/markdown-remark and handle its breaking changes
#12533 1b61fdf Thanks @ematipico! - Fixes a case where the MDX renderer couldn't be loaded when used as a direct dependency of an Astro integration.
Updated dependencies [3ab3b4e, 5608338, 560ef15, 83a2a64, 3ab3b4e, a19530e]:
- @astrojs/markdown-remark@6.0.0

withastro/astro (@astrojs/svelte)

`v9.0.1`

Compare Source

Patch Changes

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

`v9.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 '@&#8203;astrojs/react';
+ import { getContainerRenderer } from '@&#8203;astrojs/react/container-renderer';
```
Importing getContainerRenderer() from the package root still works, but is now deprecated and logs a warning.
#16549 9d9d516 Thanks @ocavue! - Updates @sveltejs/vite-plugin-svelte to v7. No user action is necessary.

Patch Changes

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

`v8.1.2`

Compare Source

Patch Changes

#16496 4d79750 Thanks @fkatsuhiro! - Fixed an issue where type errors occurred during testing library type checks because Astro overrides Svelte 5 component types.

`v8.1.1`

Compare Source

Patch Changes

#16642 53059be Thanks @ocavue! - Adds support for TypeScript v6 to peer dependencies range.

`v8.1.0`

Compare Source

Minor Changes

#16466 31b6198 Thanks @fkatsuhiro! - This change updates the Svelte integration's type shims to treat non-children
snippet props and any-typed props as optional. Previously, these were
incorrectly marked as required in Astro files, causing false-positive type
errors when using Svelte 5 components.
- Adds HandleSnippetProps to make Snippets optional in Astro.
- Distinguishes between generic and non-generic components to preserve inference.
- Updates TSX generation to apply the appropriate directive wrapper.

`v8.0.5`

Compare Source

Patch Changes

#16210 e030bd0 Thanks @matthewp! - Fixes .svelte files in node_modules failing with Unknown file extension ".svelte" when using the Cloudflare adapter with prerenderEnvironment: 'node'

`v8.0.4`

Compare Source

Patch Changes

#15604 3e1ac66 Thanks @pierreeurope! - Adds a temporary workaround for a Svelte bug causing empty class attributes in SSR output.
#16050 89a7250 Thanks @seroperson! - Using a Svelte component with generic type parameters now correctly infer props in .astro files

`v8.0.3`

Compare Source

Patch Changes

#15961 7e8d0ee Thanks @matthewp! - Fix Cloudflare dev SSR dependency optimization to compile .svelte.js and .svelte.ts dependency modules that use Svelte runes.

`v8.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

`v8.0.1`

Compare Source

Patch Changes

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

`v8.0.0`

Compare Source

Major Changes

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

Minor Changes

#14821 48ea241 Thanks @ocavue! - Update @sveltejs/vite-plugin-svelte to v6.

Patch Changes

#15125 6feb0d7 Thanks [@florian-lefebvre](https://redirect.github.com/flori

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone Europe/Zurich)

Branch creation
- "before 5am on Monday"
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.

vercel · 2024-12-02T00:04:31Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
noahflk-com	Error		Jul 16, 2026 5:54pm

renovate Bot added breaking dependencies labels Dec 2, 2024

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 1db6699 to a092a75 Compare December 2, 2024 03:25

vercel Bot had a problem deploying to Preview December 2, 2024 03:25 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from a092a75 to a0d2f89 Compare December 9, 2024 01:41

vercel Bot had a problem deploying to Preview December 9, 2024 01:41 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from a0d2f89 to 8ab2756 Compare December 10, 2024 12:38

renovate Bot changed the title ~~Update dependency @astrojs/svelte to v6~~ Update astro monorepo (major) Dec 10, 2024

vercel Bot had a problem deploying to Preview December 10, 2024 12:39 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 8ab2756 to b8ccb54 Compare December 11, 2024 00:33

vercel Bot had a problem deploying to Preview December 11, 2024 00:33 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from b8ccb54 to 4344313 Compare December 12, 2024 16:54

vercel Bot had a problem deploying to Preview December 12, 2024 16:55 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 4344313 to ac5dcaa Compare December 16, 2024 03:52

vercel Bot had a problem deploying to Preview December 16, 2024 03:52 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from ac5dcaa to b069a34 Compare December 16, 2024 16:06

vercel Bot had a problem deploying to Preview December 16, 2024 16:06 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from b069a34 to e21c3ae Compare December 18, 2024 11:11

vercel Bot had a problem deploying to Preview December 18, 2024 11:12 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from e21c3ae to 882f440 Compare December 23, 2024 16:02

vercel Bot had a problem deploying to Preview December 23, 2024 16:03 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 882f440 to e3acdd3 Compare December 23, 2024 18:11

vercel Bot had a problem deploying to Preview December 23, 2024 18:11 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from e3acdd3 to 17d9ca7 Compare December 23, 2024 22:52

vercel Bot had a problem deploying to Preview December 23, 2024 22:52 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 17d9ca7 to 0390975 Compare December 24, 2024 04:59

vercel Bot had a problem deploying to Preview December 24, 2024 05:00 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 0390975 to aeb1852 Compare December 26, 2024 12:43

vercel Bot had a problem deploying to Preview December 26, 2024 12:44 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 1a8bb93 to 74d1385 Compare January 20, 2025 17:25

vercel Bot had a problem deploying to Preview January 20, 2025 17:25 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 74d1385 to 37335cf Compare January 22, 2025 09:19

vercel Bot had a problem deploying to Preview January 22, 2025 09:19 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 37335cf to 7272256 Compare January 27, 2025 20:58

vercel Bot had a problem deploying to Preview January 27, 2025 20:59 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 7272256 to 3f4dd10 Compare January 30, 2025 19:04

vercel Bot had a problem deploying to Preview January 30, 2025 19:04 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 3f4dd10 to 399f403 Compare February 3, 2025 12:37

vercel Bot had a problem deploying to Preview February 3, 2025 12:37 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 399f403 to f4ae24b Compare February 6, 2025 15:07

vercel Bot had a problem deploying to Preview February 6, 2025 15:07 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from f4ae24b to 573792b Compare February 6, 2025 16:36

vercel Bot had a problem deploying to Preview February 6, 2025 16:37 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 573792b to dfc53d1 Compare February 7, 2025 12:41

vercel Bot had a problem deploying to Preview February 7, 2025 12:41 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from dfc53d1 to e80c7ed Compare February 7, 2025 18:13

vercel Bot had a problem deploying to Preview February 7, 2025 18:13 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from e80c7ed to c637811 Compare February 11, 2025 11:11

vercel Bot had a problem deploying to Preview February 11, 2025 11:11 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from c637811 to 3590195 Compare February 11, 2025 19:39

vercel Bot had a problem deploying to Preview February 11, 2025 19:39 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 3590195 to 99f44ce Compare February 17, 2025 03:12

vercel Bot had a problem deploying to Preview February 17, 2025 03:12 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 99f44ce to 3ae6188 Compare February 19, 2025 12:35

vercel Bot had a problem deploying to Preview February 19, 2025 12:35 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 3ae6188 to 63e384d Compare February 20, 2025 16:26

vercel Bot had a problem deploying to Preview February 20, 2025 16:26 Failure

renovate Bot force-pushed the renovate/major-astro-monorepo branch from 63e384d to bea20e5 Compare March 3, 2025 18:12

Update astro monorepo

cca583b

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update astro monorepo (major)#103

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

renovate Bot commented Dec 2, 2024 •

edited

Loading

Uh oh!

vercel Bot commented Dec 2, 2024 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Dec 2, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

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

Major Changes

Minor Changes

Patch Changes

Patch Changes

Major Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Minor Changes

Patch Changes

Configuration

Uh oh!

vercel Bot commented Dec 2, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

renovate Bot commented Dec 2, 2024 •

edited

Loading

vercel Bot commented Dec 2, 2024 •

edited

Loading