fix(deps): update astro monorepo #777

renovate · 2025-05-22T16:26:37Z

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

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/check (source)	`0.9.5` → `0.9.6`
@astrojs/node (source)	`9.2.2` → `9.5.1`
@astrojs/svelte (source)	`7.0.13` → `7.2.5`
astro (source)	`5.7.14` → `5.16.7`

Release Notes

withastro/astro (@astrojs/check)

`v0.9.6`

Patch Changes

#14740 abfed97 Thanks @ArmandPhilippot! - Fixes link targets in documentation following repository relocation.
Updated dependencies [abfed97]:
- @astrojs/language-server@2.16.1

withastro/astro (@astrojs/node)

Minor Changes

#14441 62ec8ea Thanks @upsuper! - Updates redirect handling to be consistent across static and server output, aligning with the behavior of other adapters.

Previously, the Node.js adapter used default HTML files with meta refresh tags when in static output. This often resulted in an extra flash of the page on redirect, while also not applying the proper status code for redirections. It's also likely less friendly to search engines.

This update ensures that configured redirects are always handled as HTTP redirects regardless of output mode, and the default HTML files for the redirects are no longer generated in static output. It makes the Node.js adapter more consistent with the other official adapters.

No change to your project is required to take advantage of this new adapter functionality. It is not expected to cause any breaking changes. However, if you relied on the previous redirecting behavior, you may need to handle your redirects differently now. Otherwise you should notice smoother redirects, with more accurate HTTP status codes, and may potentially see some SEO gains.

`v9.4.6`

Compare Source

Patch Changes

#14514 66a26d7 Thanks @matthewp! - Fixes compatibility issue with older versions of Astro by making getAllowedDomains() call optional and updating peer dependency to require astro@^5.14.3

`v9.4.5`

Compare Source

Patch Changes

Updated dependencies [b8ca69b]:
- @astrojs/internal-helpers@0.7.4

`v9.4.4`

Compare Source

Patch Changes

Updated dependencies [1e2499e]:
- @astrojs/internal-helpers@0.7.3

`v9.4.3`

Compare Source

Patch Changes

#14240 77b18fb Thanks @delucis! - Increases the minimum supported version of Astro to 5.7.0

`v9.4.2`

Compare Source

Patch Changes

Updated dependencies [4d16de7]:
- @astrojs/internal-helpers@0.7.2

`v9.4.1`

Compare Source

Patch Changes

5fc3c59 Thanks @ematipico! - Fixes a routing bug in standalone mode with trailingSlash set to "always".

`v9.4.0`

Compare Source

Minor Changes

#14188 e3422aa Thanks @ascorbic! - Adds support for specifying a host to load prerendered error pages

By default, if a user defines a custom error page that is prerendered, Astro will load it from the same host as the one that the request is made to. This change allows users to specify a different host for loading prerendered error pages. This can be useful in scenarios such as where the server is running behind a reverse proxy or when prerendered pages are hosted on a different domain.

To use this feature, set the experimentalErrorPageHost adapter option in your Astro configuration to the desired host URL. For example, if your server is running on localhost and served via a proxy, you can ensure the prerendered error pages are fetched via the localhost URL:
```
import { defineConfig } from 'astro/config';
import node from '@&#8203;astrojs/node';
export default defineConfig({
  adapter: node({
    // If your server is running on localhost and served via a proxy, set the host like this to ensure prerendered error pages are fetched via the localhost URL
    experimentalErrorPageHost: 'http://localhost:4321',
  }),
});
```
For more information on enabling and using this experimental feature, see the @astrojs/node adapter docs.

`v9.3.3`

Compare Source

Patch Changes

Updated dependencies [0567fb7]:
- @astrojs/internal-helpers@0.7.1

`v9.3.2`

Compare Source

Patch Changes

Updated dependencies [f4e8889]:
- @astrojs/internal-helpers@0.7.0

`v9.3.1`

Compare Source

Patch Changes

#14148 e4d74ba Thanks @ColoredCarrot! - fix(node): emit set-cookie header from middlewares for not-found routes (#14136)

`v9.3.0`

Compare Source

Minor Changes

#14012 a125a14 Thanks @florian-lefebvre! - Adds a new experimental configuration option experimentalDisableStreaming to allow you to opt out of Astro's default HTML streaming for pages rendered on demand.

HTML streaming helps with performance and generally provides a better visitor experience. In most cases, disabling streaming is not recommended.

However, when you need to disable HTML streaming (e.g. your host only supports non-streamed HTML caching at the CDN level), you can now opt out of the default behavior:
```
import { defineConfig } from 'astro/config';
import node from '@&#8203;astrojs/node';

export default defineConfig({
  adapter: node({
    mode: 'standalone',
+    experimentalDisableStreaming: true,
  }),
});
```
#13972 db8f8be Thanks @ematipico! - Adds support for the experimental static headers Astro feature.

When the feature is enabled via the option experimentalStaticHeaders, and experimental Content Security Policy is enabled, the adapter will generate Response headers for static pages, which allows support for CSP directives that are not supported inside a <meta> tag (e.g. frame-ancestors).
```
import { defineConfig } from 'astro/config';
import node from '@&#8203;astrojs/node';

export default defineConfig({
  adapter: node({
    mode: 'standalone',
    experimentalStaticHeaders: true,
  }),
  experimental: {
    cps: true,
  },
});
```

withastro/astro (@astrojs/svelte)

`v7.2.5`

Compare Source

Patch Changes

#15070 fa9c464 Thanks @antonyfaris! - Improve Svelte children prop type checking

`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

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

`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

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

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

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. Additionally, you may also specify any additional file formats to download if available:

// astro.config.mjs
import { defineConfig, fontProviders } from 'astro/config'

export default defineConfig({
    experimental: {
        fonts: [{
            name: 'Roboto',
            cssVariable: '--font-roboto',
            provider: fontProviders.google(),
+            formats: ['woff2', 'woff', 'otf']
        }]
    }
})

#15034 8115752 Thanks @florian-lefebvre! - Fixes a vite warning log during builds when using npm

`v5.16.6`

Compare Source

Patch Changes

#14982 6849e38 Thanks @Princesseuh! - Fixes images outside the project directory not working when using astro:assets in development mode
#14987 9dd9fca Thanks @Princesseuh! - Fixes SVGs not working in dev mode when using the passthrough image service
#15014 a178422 Thanks @delucis! - Adds support for extending the type of the props accepted by Astro’s <Image> component, <Picture> component, and getImage() API.

`v5.16.5`

Compare Source

Patch Changes

#14985 c016f10 Thanks @florian-lefebvre! - Fixes a case where JSDoc annotations wouldn't show for fonts related APIs in the Astro config
#14973 ed7cc2f Thanks @amankumarpandeyin! - Fixes performance regression and OOM errors when building medium-sized blogs with many content entries. Replaced O(n²) object spread pattern with direct mutation in generateLookupMap.
#14958 70eb542 Thanks @ascorbic! - Gives a helpful error message if a user sets output: "hybrid" in their Astro config.

The option was removed in Astro 5, but lots of content online still references it, and LLMs often suggest it. It's not always clear that the replacement is output: "static", rather than output: "server". This change adds a helpful error message to guide humans and robots.
#14901 ef53716 Thanks @Darknab! - Updates the glob() loader to log a warning when duplicated IDs are detected
Updated dependencies [d8305f8]:
- @astrojs/markdown-remark@6.3.10

`v5.16.4`

Compare Source

Patch Changes

#14940 2cf79c2 Thanks @ematipico! - Fixes a bug where Astro didn't properly combine CSP resources from the csp configuration with those added using the runtime API (Astro.csp.insertDirective()) to form grammatically correct CSP headers

Now Astro correctly deduplicate CSP resources. For example, if you have a global resource in the configuration file, and then you add a
a new one using the runtime APIs.

`v5.16.3`

Compare Source

Patch Changes

#14889 4bceeb0 Thanks @florian-lefebvre! - Fixes actions types when using specific TypeScript configurations
#14929 e0f277d Thanks @matthewp! - Fixes authentication bypass via double URL encoding in middleware

Prevents attackers from bypassing path-based authentication checks using multi-level URL encoding (e.g., /%2561dmin instead of /%61dmin). Pathnames are now validated after decoding to ensure no additional encoding remains.

`v5.16.2`

Compare Source

Patch Changes

#14876 b43dc7f Thanks @florian-lefebvre! - Fixes a vite warning log during builds when using npm
#14884 10273e0 Thanks @florian-lefebvre! - Fixes a case where setting the status of a page to 404 in ssr would show an empty page (or 404.astro page if provided) instead of using the current page

`v5.16.1`

Compare Source

Patch Changes

#14769 b43ee71 Thanks @adriandlam! - Fixes an unhandled rejection issue when using Astro with Vercel Workflow DevKit
#14761 345eb22 Thanks @ooga! - Updates button attributes types to allow command and commandfor
#14866 65e214b Thanks @GameRoMan! - Fixes Astro.glob to be correctly marked as deprecated
#14894 1ad9a5b Thanks @delucis! - Fixes support for Astro component rendering in Vitest test suites using a “client” environment such as happy-dom or jsdom
#14782 abed929 Thanks @florian-lefebvre! - Improves syncing

`v5.16.0`

Compare Source

Minor Changes

#13880 1a2ed01 Thanks @azat-io! - Adds experimental SVGO optimization support for SVG assets

Astro now supports automatic SVG optimization using SVGO during build time. This experimental feature helps reduce SVG file sizes while maintaining visual quality, improving your site's performance.

To enable SVG optimization with default settings, add the following to your astro.config.mjs:
```
import { defineConfig } from 'astro/config';

export default defineConfig({
  experimental: {
    svgo: true,
  },
});
```
To customize optimization, pass a SVGO configuration object:
```
export default defineConfig({
  experimental: {
    svgo: {
      plugins: [
        'preset-default',
        {
          name: 'removeViewBox',
          active: false,
        },
      ],
    },
  },
});
```
For more information on enabling and using this feature in your project, see the experimental SVG optimization docs.
#14810 2e845fe Thanks @ascorbic! - Adds a hint for code agents to use the --yes flag to skip prompts when running astro add

#14698 f42ff9b Thanks @mauriciabad! - Adds the ActionInputSchema utility type to automatically infer the TypeScript type of an action's input based on its Zod schema

For example, this type can be used to retrieve the input type of a form action:

import { type ActionInputSchema, defineAction } from 'astro:actions';
import { z } from 'astro/zod';

const action = defineAction({
  accept: 'form',
  input: z.object({ name: z.string() }),
  handler: ({ name }) => ({ message: `Welcome, ${name}!` }),
});

type Schema = ActionInputSchema<typeof action>;
// typeof z.object({ name: z.string() })

type Input = z.input<Schema>;
// { name: string }

#14574 4356485 Thanks @jacobdalamb! - Adds new CLI shortcuts available when running astro preview:
- o + enter: open the site in your browser
- q + enter: quit the preview
- h + enter: print all available shortcuts

Patch Changes

#14813 e1dd377 Thanks @ematipico! - Removes picocolors as dependency in favor of the fork piccolore.
#14609 d774306 Thanks @florian-lefebvre! - Improves astro info
#14796 c29a785 Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

Updates the default subsets to ["latin"]

Subsets have been a common source of confusion: they caused a lot of files to be downloaded by default. You now have to manually pick extra subsets.

Review your Astro config and update subsets if you need, for example if you need greek characters:
```
import { defineConfig, fontProviders } from "astro/config"

export default defineConfig({
    experimental: {
        fonts: [{
            name: "Roboto",
            cssVariable: "--font-roboto",
            provider: fontProviders.google(),
+            subsets: ["latin", "greek"]
        }]
    }
})
```

`v5.15.9`

Compare Source

Patch Changes

#14786 758a891 Thanks @mef! - Add handling of invalid encrypted props and slots in server islands.
#14783 504958f Thanks @florian-lefebvre! - Improves the experimental Fonts API build log to show the number of downloaded files. This can help spotting excessive downloading because of misconfiguration
#14791 9e9c528 Thanks @Princesseuh! - Changes the remote protocol checks for images to require explicit authorization in order to use data URIs.

In order to allow data URIs for remote images, you will need to update your astro.config.mjs file to include the following configuration:
```
// astro.config.mjs
import { defineConfig } from 'astro/config';

export default defineConfig({
  images: {
    remotePatterns: [
      {
        protocol: 'data',
      },
    ],
  },
});
```
#14787 0f75f6b Thanks @matthewp! - Fixes wildcard hostname pattern matching to correctly reject hostnames without dots

Previously, hostnames like localhost or other single-part names would incorrectly match patterns like *.example.com. The wildcard matching logic has been corrected to ensure that only valid subdomains matching the pattern are accepted.
#14776 3537876 Thanks @ktym4a! - Fixes the behavior of passthroughImageService so it does not generate webp.
Updated dependencies [9e9c528, 0f75f6b]:
- @astrojs/internal-helpers@0.7.5
- @astrojs/markdown-remark@6.3.9

`v5.15.8`

Compare Source

Patch Changes

#14772 00c579a Thanks @matthewp! - Improves the security of Server Islands slots by encrypting them before transmission to the browser, matching the security model used for props. This improves the integrity of slot content and prevents injection attacks, even when component templates don't explicitly support slots.

Slots continue to work as expected for normal usage—this change has no breaking changes for legitimate requests.
#14771 6f80081 Thanks @matthewp! - Fix middleware pathname matching by normalizing URL-encoded paths

Middleware now receives normalized pathname values, ensuring that encoded paths like /%61dmin are properly decoded to /admin before middleware checks. This prevents potential security issues where middleware checks might be bypassed through URL encoding.

`v5.15.7`

Compare Source

Patch Changes

#14765 03fb47c Thanks @florian-lefebvre! - Fixes a case where process.env wouldn't be properly populated during the build
#14690 ae7197d Thanks @fredriknorlin! - Fixes a bug where Astro's i18n fallback system with fallbackType: 'rewrite' would not generate fallback files for pages whose filename started with a locale key.

`v5.15.6`

Compare Source

Patch Changes

#14751 18c55e1 Thanks @delucis! - Fixes hydration of client components when running the dev server and using a barrel file that re-exports both Astro and UI framework components.
#14750 35122c2 Thanks @florian-lefebvre! - Updates the experimental Fonts API to log a warning if families with a conflicting cssVariable are provided
#14737 74c8852 Thanks @Arecsu! - Fixes an error when using transition:persist with components that use declarative Shadow DOM. Astro now avoids re-attaching a shadow root if one already exists, preventing "Unable to re-attach to existing ShadowDOM" navigation errors.
#14750 35122c2 Thanks @florian-lefebvre! - Updates the experimental Fonts API to allow for more granular configuration of remote font families

A font family is defined by a combination of properties such as weights and styles (e.g. weights: [500, 600] and styles: ["normal", "bold"]), but you may want to download only certain combinations of these.

For greater control over which font files are downloaded, you can specify the same font (ie. with the same cssVariable, name, and provider properties) multiple times with different combinations. Astro will merge the results and download only the required files. For example, it is possible to download normal 500 and 600 while downloading only italic 500:
```
// astro.config.mjs
import { defineConfig, fontProviders } from 'astro/config';

export default defineConfig({
  experimental: {
    fonts: [
      {
        name: 'Roboto',
        cssVariable: '--roboto',
        provider: fontProviders.google(),
        weights: [500, 600],
        styles: ['normal'],
      },
      {
        name: 'Roboto',
        cssVariable: '--roboto',
        provider: fontProviders.google(),
        weights: [500],
        styles: ['italic'],
      },
    ],
  },
});
```

`v5.15.5`

Compare Source

Patch Changes

#14712 91780cf Thanks @florian-lefebvre! - Fixes a case where build's process.env would be inlined in the server output
#14713 666d5a7 Thanks @florian-lefebvre! - Improves fallbacks generation when using the experimental Fonts API
#14743 dafbb1b Thanks @matthewp! - Improves X-Forwarded header validation to prevent cache poisoning and header injection attacks. Now properly validates X-Forwarded-Proto, X-Forwarded-Host, and X-Forwarded-Port headers against configured allowedDomains patterns, rejecting malformed or suspicious values. This is especially important when running behind a reverse proxy or load balancer.

`v5.15.4`

Compare Source

Patch Changes

#14703 970ac0f Thanks @ArmandPhilippot! - Adds missing documentation for some public utilities exported from astro:i18n.
#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.
#14711 a4d284d Thanks @deining! - Fixes typos in documenting our error messages and public APIs.
#14701 9be54c7 Thanks @florian-lefebvre! - Fixes a case where the experimental Fonts API would filter available font files too aggressively, which could prevent the download of woff files when using the google provider

`v5.15.3`

Compare Source

Patch Changes

#14627 b368de0 Thanks @matthewp! - Fixes skew protection support for images and font URLs

Adapter-level query parameters (assetQueryParams) are now applied to all image and font asset URLs, including:
- Dynamic optimized images via /_image endpoint
- Static optimized image files
- Font preload tags and font requests when using the experimental Fonts API
#14631 3ad33f9 Thanks @KurtGokhan! - Adds the astro/jsx-dev-runtime export as an alias for astro/jsx-runtime

`v5.15.2`

Compare Source

Patch Changes

#14623 c5fe295 Thanks @delucis! - Fixes a leak of server runtime code when importing SVGs in client-side code. Previously, when importing an SVG file in client code, Astro could end up adding code for rendering SVGs on the server to the client bundle.
#14621 e3175d9 Thanks @GameRoMan! - Updates vite version to fix CVE

`v5.15.1`

Compare Source

Patch Changes

#14612 18552c7 Thanks @ematipico! - Fixes a regression introduced in Astro v5.14.7 that caused ?url imports to not work correctly. This release reverts #14142.

`v5.15.0`

Compare Source

Minor Changes

#14543 9b3241d Thanks @matthewp! - Adds two new adapter configuration options assetQueryParams and internalFetchHeaders to the Adapter API.

Official and community-built adapters can now use client.assetQueryParams to specify query parameters that should be appended to asset URLs (CSS, JavaScript, images, fonts, etc.). The query parameters are automatically appended to all generated asset URLs during the build process.

Adapters can also use client.internalFetchHeaders to specify headers that should be included in Astro's internal fetch calls (Actions, View Transitions, Server Islands, Prefetch).

This enables features like Netlify's skew protection, which requires the deploy ID to be sent with both internal requests and asset URLs to ensure client and server versions match during deployments.
#14489 add4277 Thanks @dev-shetty! - Adds a new Copy to Clipboard button to the error overlay stack trace.

When an error occurs in dev mode, you can now copy the stack trace with a single click to more easily share it in a bug report, a support thread, or with your favorite LLM.
[#14564](https://redirect.github.com/withastro/astro/pull/145

Configuration

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

🚦 Automerge: Enabled.

♻ 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-05-22T16:27:08Z

Deploying website with Cloudflare Pages

Latest commit:	`1527d84`
Status:	🚫 Build failed.

View logs

renovate bot enabled auto-merge (squash) May 22, 2025 16:26

gitstream-cm bot added 1 min review dependencies labels May 22, 2025

renovate bot force-pushed the renovate/astro-monorepo branch 14 times, most recently from 2cb93ff to d203349 Compare May 29, 2025 22:41

renovate bot force-pushed the renovate/astro-monorepo branch 12 times, most recently from abf35e4 to 68e213d Compare June 4, 2025 13:01

renovate bot force-pushed the renovate/astro-monorepo branch 9 times, most recently from 08ce2ba to a2e6509 Compare December 10, 2025 19:31

renovate bot force-pushed the renovate/astro-monorepo branch 9 times, most recently from 7b34416 to ed6fdca Compare December 16, 2025 13:05

renovate bot force-pushed the renovate/astro-monorepo branch 5 times, most recently from b092082 to 3406945 Compare December 24, 2025 14:02

renovate bot force-pushed the renovate/astro-monorepo branch 4 times, most recently from 8f28271 to bb93f31 Compare December 31, 2025 01:52

renovate bot force-pushed the renovate/astro-monorepo branch from bb93f31 to bb62054 Compare January 7, 2026 14:45

fix(deps): update astro monorepo

1527d84

renovate bot force-pushed the renovate/astro-monorepo branch from bb62054 to 1527d84 Compare January 8, 2026 19:42

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): update astro monorepo #777

fix(deps): update astro monorepo #777

Uh oh!

renovate bot commented May 22, 2025 •

edited

Loading

Uh oh!

cloudflare-workers-and-pages bot commented May 22, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

fix(deps): update astro monorepo #777

Are you sure you want to change the base?

fix(deps): update astro monorepo #777

Uh oh!

Conversation

renovate bot commented May 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

What should I do?

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

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Configuration

Uh oh!

cloudflare-workers-and-pages bot commented May 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploying website with Cloudflare Pages

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate bot commented May 22, 2025 •

edited

Loading

cloudflare-workers-and-pages bot commented May 22, 2025 •

edited

Loading