Skip to content

fix(deps): update astro monorepo#24

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/astro-monorepo
Open

fix(deps): update astro monorepo#24
renovate[bot] wants to merge 1 commit intomainfrom
renovate/astro-monorepo

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 26, 2025 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@astrojs/cloudflare (source) 13.0.0-beta.1 → 13.0.0-beta.12 age confidence
astro (source) 6.0.0-beta.3 → 6.0.0-beta.18 age confidence

Release Notes

withastro/astro (@​astrojs/cloudflare)

v13.0.0-beta.12

Compare Source

Patch Changes

v13.0.0-beta.11

Compare Source

Patch Changes

v13.0.0-beta.10

Compare Source

Patch Changes

v13.0.0-beta.9

Compare Source

Major Changes
Minor Changes

  • #​15435 957b9fe Thanks @​rururux! - Adds support for configuring the image service as an object with separate build and runtime options

    It is now possible to set both a build-time and runtime service independently. Currently, 'compile' is the only available build time option. The supported runtime options are 'passthrough' (default) and 'cloudflare-binding':

    import { defineConfig } from 'astro/config';
import cloudflare from '@​astrojs/cloudflare';

export default defineConfig({
  adapter: cloudflare({
    imageService: { build: 'compile', runtime: 'cloudflare-binding' },
  }),
});

    See the Cloudflare adapter imageService docs for more information about configuring your image service.

  • #​15556 8fb329b Thanks @​florian-lefebvre! - Adds support for more @cloudflare/vite-plugin options

    The adapter now accepts the following options from Cloudflare's Vite plugin:

    • auxiliaryWorkers
    • configPath
    • inspectorPort
    • persistState
    • remoteBindings
    • experimental.headersAndRedirectsDevModeSupport

    For example, you can now set inspectorPort to provide a custom port for debugging your Workers:

    // astro.config.mjs
import { defineConfig } from 'astro/config';
import cloudflare from '@​astrojs/cloudflare';

export default defineConfig({
  adapter: cloudflare({
    inspectorPort: 3456,
  }),
});
Patch Changes

v13.0.0-beta.8

Compare Source

Major Changes

  • #​15480 e118214 Thanks @​alexanderniebuhr! - Drops official support for Cloudflare Pages in favor of Cloudflare Workers

    The Astro Cloudflare adapter now only supports deployment to Cloudflare Workers by default in order to comply with Cloudflare's recommendations for new projects. If you are currently deploying to Cloudflare Pages, consider migrating to Workers by following the Cloudflare guide for an optimal experience and full feature support.

Patch Changes

v13.0.0-beta.7

Compare Source

Patch Changes

  • #​15452 e1aa3f3 Thanks @​matthewp! - Fixes server-side dependencies not being discovered ahead of time during development

    Previously, imports in .astro file frontmatter were not scanned by Vite's dependency optimizer, causing a "new dependencies optimized" message and page reload when the dependency was first encountered. Astro is now able to scan these dependencies ahead of time.

  • #​15450 50c9129 Thanks @​florian-lefebvre! - Fixes a case where build.serverEntry would not be respected when using the new Adapter API

  • Updated dependencies []:

v13.0.0-beta.6

Compare Source

Major Changes

  • #​15345 840fbf9 Thanks @​matthewp! - Removes the cloudflareModules adapter option

    The cloudflareModules option has been removed because it is no longer necessary. Cloudflare natively supports importing .sql, .wasm, and other module types.

What should I do?

Remove the cloudflareModules option from your Cloudflare adapter configuration if you were using it:

import cloudflare from '@​astrojs/cloudflare';

export default defineConfig({
  adapter: cloudflare({
-   cloudflareModules: true
  })
});
Minor Changes

  • #​15077 a164c77 Thanks @​matthewp! - Adds support for prerendering pages using the workerd runtime.

    The Cloudflare adapter now uses the new setPrerenderer() API to prerender pages via HTTP requests to a local preview server running workerd, instead of using Node.js. This ensures prerendered pages are built using the same runtime that serves them in production.

Patch Changes

v13.0.0-beta.5

Compare Source

Major Changes
Patch Changes

v13.0.0-beta.4

Compare Source

Patch Changes

v13.0.0-beta.3

Compare Source

Patch Changes

  • #​15336 9cce92e Thanks @​ascorbic! - Fixes a dev server issue where framework components from linked packages would fail to load with a 504 error.

    This could occur when using client:only or other client directives with components from monorepo packages (linked via file: or workspace protocol). The first request would trigger Vite's dependency optimizer mid-request, causing concurrent client module requests to fail.

  • Updated dependencies []:

v13.0.0-beta.2

Compare Source

Patch Changes
withastro/astro (astro)

v6.0.0-beta.18

Compare Source

Major Changes
Minor Changes

  • #​15694 66449c9 Thanks @​matthewp! - Adds preserveBuildClientDir option to adapter features

    Adapters can now opt in to preserving the client/server directory structure for static builds by setting preserveBuildClientDir: true in their adapter features. When enabled, static builds will output files to build.client instead of directly to outDir.

    This is useful for adapters that require a consistent directory structure regardless of the build output type, such as deploying to platforms with specific file organization requirements.

    // my-adapter/index.js
export default function myAdapter() {
  return {
    name: 'my-adapter',
    hooks: {
      'astro:config:done': ({ setAdapter }) => {
        setAdapter({
          name: 'my-adapter',
          adapterFeatures: {
            buildOutput: 'static',
            preserveBuildClientDir: true,
          },
        });
      },
    },
  };
}

  • #​15579 08437d5 Thanks @​ascorbic! - Adds two new experimental flags for a Route Caching API and further configuration-level Route Rules for controlling SSR response caching.

    Route caching gives you a platform-agnostic way to cache server-rendered responses, based on web standard cache headers. You set caching directives in your routes using Astro.cache (in .astro pages) or context.cache (in API routes and middleware), and Astro translates them into the appropriate headers or runtime behavior depending on your adapter. You can also define cache rules for routes declaratively in your config using experimental.routeRules, without modifying route code.

    This feature requires on-demand rendering. Prerendered pages are already static and do not use route caching.

Getting started

Enable the feature by configuring experimental.cache with a cache provider in your Astro config:

// astro.config.mjs
import { defineConfig } from 'astro/config';
import node from '@​astrojs/node';
import { memoryCache } from 'astro/config';

export default defineConfig({
  adapter: node({ mode: 'standalone' }),
  experimental: {
    cache: {
      provider: memoryCache(),
    },
  },
});
Using Astro.cache and context.cache

In .astro pages, use Astro.cache.set() to control caching:

---
// src/pages/index.astro
Astro.cache.set({
  maxAge: 120, // Cache for 2 minutes
  swr: 60, // Serve stale for 1 minute while revalidating
  tags: ['home'], // Tag for targeted invalidation
});
---

<html><body>Cached page</body></html>

In API routes and middleware, use context.cache:

// src/pages/api/data.ts
export function GET(context) {
  context.cache.set({
    maxAge: 300,
    tags: ['api', 'data'],
  });
  return Response.json({ ok: true });
}
Cache options

cache.set() accepts the following options:

  • maxAge (number): Time in seconds the response is considered fresh.
  • swr (number): Stale-while-revalidate window in seconds. During this window, stale content is served while a fresh response is generated in the background.
  • tags (string[]): Cache tags for targeted invalidation. Tags accumulate across multiple set() calls within a request.
  • lastModified (Date): When multiple set() calls provide lastModified, the most recent date wins.
  • etag (string): Entity tag for conditional requests.

Call cache.set(false) to explicitly opt out of caching for a request.

Multiple calls to cache.set() within a single request are merged: scalar values use last-write-wins, lastModified uses most-recent-wins, and tags accumulate.

Invalidation

Purge cached entries by tag or path using cache.invalidate():

// Invalidate all entries tagged 'data'
await context.cache.invalidate({ tags: ['data'] });

// Invalidate a specific path
await context.cache.invalidate({ path: '/api/data' });
Config-level route rules

Use experimental.routeRules to set default cache options for routes without modifying route code. Supports Nitro-style shortcuts for ergonomic configuration:

import { memoryCache } from 'astro/config';

export default defineConfig({
  experimental: {
    cache: {
      provider: memoryCache(),
    },
    routeRules: {
      // Shortcut form (Nitro-style)
      '/api/*': { swr: 600 },

      // Full form with nested cache
      '/products/*': { cache: { maxAge: 3600, tags: ['products'] } },
    },
  },
});

Route patterns support static paths, dynamic parameters ([slug]), and rest parameters ([...path]). Per-route cache.set() calls merge with (and can override) the config-level defaults.

You can also read the current cache state via cache.options:

const { maxAge, swr, tags } = context.cache.options;
Cache providers

Cache behavior is determined by the configured cache provider. There are two types:

  • CDN providers set response headers (e.g. CDN-Cache-Control, Cache-Tag) and let the CDN handle caching. Astro strips these headers before sending the response to the client.
  • Runtime providers implement onRequest() to intercept and cache responses in-process, adding an X-Astro-Cache header (HIT/MISS/STALE) for observability.
Built-in memory cache provider

Astro includes a built-in, in-memory LRU runtime cache provider. Import memoryCache from astro/config to configure it.

Features:

  • In-memory LRU cache with configurable max entries (default: 1000)
  • Stale-while-revalidate support
  • Tag-based and path-based invalidation
  • X-Astro-Cache response header: HIT, MISS, or STALE
  • Query parameter sorting for better hit rates (?b=2&a=1 and ?a=1&b=2 hit the same entry)
  • Common tracking parameters (utm_*, fbclid, gclid, etc.) excluded from cache keys by default
  • Vary header support — responses that set Vary automatically get separate cache entries per variant
  • Configurable query parameter filtering via query.exclude (glob patterns) and query.include (allowlist)

For more information on enabling and using this feature in your project, see the Experimental Route Caching docs.
For a complete overview and to give feedback on this experimental API, see the Route Caching RFC.

Patch Changes

  • #​15721 e6e146c Thanks @​matthewp! - Fixes action route handling to return 404 for requests to prototype method names like constructor or toString used as action paths

  • #​15704 862d77b Thanks @​umutkeltek! - Fixes i18n fallback middleware intercepting non-404 responses

    The fallback middleware was triggering for all responses with status >= 300, including legitimate 3xx redirects, 403 forbidden, and 5xx server errors. This broke auth flows and form submissions on localized server routes. The fallback now correctly only triggers for 404 (page not found) responses.

  • #​15703 829182b Thanks @​matthewp! - Fixes server islands returning a 500 error in dev mode for adapters that do not set adapterFeatures.buildOutput (e.g. @astrojs/netlify)

  • #​15749 573d188 Thanks @​ascorbic! - Fixes a bug that caused session.regenerate() to silently lose session data

    Previously, regenerated session data was not saved under the new session ID unless set() was also called.

  • #​15685 1a323e5 Thanks @​jcayzac! - Fix regression where SVG images in content collection image() fields could not be rendered as inline components. This behavior is now restored while preserving the TLA deadlock fix.

  • #​15740 c5016fc Thanks @​matthewp! - Removes an escape hatch that skipped attribute escaping for URL values containing &, ensuring all dynamic attribute values are consistently escaped

  • #​15744 fabb710 Thanks @​matthewp! - Fixes cookie handling during error page rendering to ensure cookies set by middleware are consistently included in the response

  • #​15742 9d9699c Thanks @​matthewp! - Hardens clientAddress resolution to respect security.allowedDomains for X-Forwarded-For, consistent with the existing handling of X-Forwarded-Host, X-Forwarded-Proto, and X-Forwarded-Port. The X-Forwarded-For header is now only used to determine Astro.clientAddress when the request's host has been validated against an allowedDomains entry. Without a matching domain, clientAddress falls back to the socket's remote address.

  • #​15696 a9fd221 Thanks @​Princesseuh! - Fixes images not working in MDX when using the Cloudflare adapter in certain cases

  • #​15693 4db2089 Thanks @​ArmandPhilippot! - Fixes the links to Astro Docs to match the v6 structure.

  • #​15717 4000aaa Thanks @​matthewp! - Ensures that URLs with multiple leading slashes (e.g. //admin) are normalized to a single slash before reaching middleware, so that pathname checks like context.url.pathname.startsWith('/admin') work consistently regardless of the request URL format

  • #​15752 918d394 Thanks @​ascorbic! - Fixes an issue where a session ID from a cookie with no matching server-side data was accepted as-is. The session now generates a new ID when the cookie value has no corresponding storage entry.

  • #​15743 3b4252a Thanks @​matthewp! - Hardens config-based redirects with catch-all parameters to prevent producing protocol-relative URLs (e.g. //example.com) in the Location header

  • #​15718 14f37b8 Thanks @​florian-lefebvre! - Fixes a case where internal headers may leak when rendering error pages

  • Updated dependencies [6f19ecc, f94d3c5]:

v6.0.0-beta.17

Compare Source

Minor Changes

  • #​15495 5b99e90 Thanks @​leekeh! - Adds a new middlewareMode adapter feature to replace the previous edgeMiddleware option.

    This feature only impacts adapter authors. If your adapter supports edgeMiddleware, you should upgrade to the new middlewareMode option to specify the middleware mode for your adapter as soon as possible. The edgeMiddleware feature is deprecated and will be removed in a future major release.

    export default function createIntegration() {
  return {
    name: '@&#8203;example/my-adapter',
    hooks: {
      'astro:config:done': ({ setAdapter }) => {
        setAdapter({
          name: '@&#8203;example/my-adapter',
          serverEntrypoint: '@&#8203;example/my-adapter/server.js',
          adapterFeatures: {
-            edgeMiddleware: true
+            middlewareMode: 'edge'
          }
        });
      },
    },
  };
}
Patch Changes

  • #​15657 cb625b6 Thanks @​qzio! - Adds a new security.actionBodySizeLimit option to configure the maximum size of Astro Actions request bodies.

    This lets you increase the default 1 MB limit when your actions need to accept larger payloads. For example, actions that handle file uploads or large JSON payloads can now opt in to a higher limit.

    If you do not set this option, Astro continues to enforce the 1 MB default to help prevent abuse.

    // astro.config.mjs
export default defineConfig({
  security: {
    actionBodySizeLimit: 10 * 1024 * 1024, // set to 10 MB
  },
});

  • Updated dependencies [1fa4177]:

v6.0.0-beta.16

Compare Source

Minor Changes

  • #​15646 0dd9d00 Thanks @​delucis! - Removes redundant fetchpriority attributes from the output of Astro’s <Image> component

    Previously, Astro would always include fetchpriority="auto" on images not using the priority attribute.
    However, this is the default value, so specifying it is redundant. This change omits the attribute by default.

Patch Changes

v6.0.0-beta.15

Compare Source

Minor Changes

  • #​15471 32b4302 Thanks @​ematipico! - Adds a new experimental flag queuedRendering to enable a queue-based rendering engine

    The new engine is based on a two-pass process, where the first pass
    traverses the tree of components, emits an ordered queue, and then the queue is rendered.

    The new engine does not use recursion, and comes with two customizable options.

    Early benchmarks showed significant speed improvements and memory efficiency in big projects.

Queue-rendered based

The new engine can be enabled in your Astro config with experimental.queuedRendering.enabled set to true, and can be further customized with additional sub-features.

// astro.config.mjs
export default defineConfig({
  experimental: {
    queuedRendering: {
      enabled: true,
    },
  },
});
Pooling

With the new engine enabled, you now have the option to have a pool of nodes that can be saved and reused across page rendering. Node pooling has no effect when rendering pages on demand (SSR) because these rendering requests don't share memory. However, it can be very useful for performance when building static pages.

// astro.config.mjs
export default defineConfig({
  experimental: {
    queuedRendering: {
      enabled: true,
      poolSize: 2000, // store up to 2k nodes to be reused across renderers
    },
  },
});
Content caching

The new engine additionally unlocks a new contentCache option. This allows you to cache values of nodes during the rendering phase. This is currently a boolean feature with no further customization (e.g. size of cache) that uses sensible defaults for most large content collections:

When disabled, the pool engine won't cache strings, but only types.

// astro.config.mjs
export default defineConfig({
  experimental: {
    queuedRendering: {
      enabled: true,
      contentCache: true, // enable re-use of node values
    },
  },
});

For more information on enabling and using this feature in your project, see the experimental queued rendering docs for more details.

  • #​15543 d43841d Thanks @​Princesseuh! - Adds a new experimental.rustCompiler flag to opt into the experimental Rust-based Astro compiler

    This experimental compiler is faster, provides better error messages, and generally has better support for modern JavaScript, TypeScript, and CSS features.

    After enabling in your Astro config, the @astrojs/compiler-rs package must also be installed into your project separately:

    import { defineConfig } from 'astro/config';

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

    This new compiler is still in early development and may exhibit some differences compared to the existing Go-based compiler. Notably, this compiler is generally more strict in regard to invalid HTML syntax and may throw errors in cases where the Go-based compiler would have been more lenient. For example, unclosed tags (e.g. <p>My paragraph) will now result in errors.

    For more information about using this experimental feature in your project, especially regarding expected differences and limitations, please see the experimental Rust compiler reference docs. To give feedback on the compiler, or to keep up with its development, see the RFC for a new compiler for Astro for more information and discussion.

Patch Changes

  • #​15565 30cd6db Thanks @​ematipico! - Fixes an issue where the use of the Astro internal logger couldn't work with Cloudflare Vite plugin.

  • #​15562 e14a51d Thanks @​florian-lefebvre! - Removes types for the astro:ssr-manifest module, which was removed

  • #​15435 957b9fe Thanks @​rururux! - Improves compatibility of the built-in image endpoint with runtimes that don't support CJS dependencies correctly

  • #​15640 4c1a801 Thanks @​ematipico! - Reverts the support of Shiki with CSP. Unfortunately, after exhaustive tests, the highlighter can't be supported to cover all cases.

    Adds a warning when both Content Security Policy (CSP) and Shiki syntax highlighting are enabled, as they are incompatible due to Shiki's use of inline styles

  • #​15605 f6473fd Thanks @​ascorbic! - Improves .astro component SSR rendering performance by up to 2x.

    This includes several optimizations to the way that Astro generates and renders components on the server. These are mostly micro-optimizations, but they add up to a significant improvement in performance. Most pages will benefit, but pages with many components will see the biggest improvement, as will pages with lots of strings (e.g. text-heavy pages with lots of HTML elements).

  • #​15514 999a7dd Thanks @​veeceey! - Fixes font flash (FOUT) during ClientRouter navigation by preserving inline <style> elements and font preload links in the head during page transitions.

    Previously, @font-face declarations from the <Font> component were removed and re-inserted on every client-side navigation, causing the browser to re-evaluate them.

  • #​15580 a92333c Thanks @​ematipico! - Fixes a build error when generating projects with a large number of static routes

  • #​15549 be1c87e Thanks @​0xRozier! - Fixes an issue where original (unoptimized) images from prerendered pages could be kept in the build output during SSR builds.

  • #​15565 30cd6db Thanks @​ematipico! - Fixes an issue where the use of the Code component would result in an unexpected error.

  • #​15585 98ea30c Thanks @​matthewp! - Add a default body size limit for server actions to prevent oversized requests from exhausting memory.

  • #​15565 30cd6db Thanks @​ematipico! - Fixes an issue where the new Astro v6 development server didn't log anything when navigating the pages.

  • #​15591 1ed07bf Thanks @​renovate! - Upgrades devalue to v5.6.3

  • #​15633 9d293c2 Thanks @​jwoyo! - Fixes a case where <script> tags from components passed as slots to server islands were not included in the response

  • #​15586 35bc814 Thanks @​matthewp! - Fixes an issue where allowlists were not being enforced when handling remote images

v6.0.0-beta.14

Compare Source

Patch Changes

  • #​15573 d789452 Thanks @​matthewp! - Clear the route cache on content changes so slug pages reflect updated data during dev.

  • #​15560 170ed89 Thanks @​z0mt3c! - Fix X-Forwarded-Proto validation when allowedDomains includes both protocol and hostname fields. The protocol check no longer fails due to hostname mismatch against the hardcoded test URL.

  • #​15563 e959698 Thanks @​ematipico! - Fixes an issue where warnings would be logged during the build using one of the official adapters

v6.0.0-beta.13

Compare Source

Major Changes
Minor Changes

  • #​15529 a509941 Thanks @​florian-lefebvre! - Adds a new build-in font provider npm to access fonts installed as NPM packages

    You can now add web fonts specified in your package.json through Astro's type-safe Fonts API. The npm font provider allows you to add fonts either from locally installed packages in node_modules or from a CDN.

    Set fontProviders.npm() as your fonts provider along with the required name and cssVariable values, and add options as needed:

    import { defineConfig, fontProviders } from 'astro/config';

export default defineConfig({
  experimental: {
    fonts: [
      {
        name: 'Roboto',
        provider: fontProviders.npm(),
        cssVariable: '--font-roboto',
      },
    ],
  },
});

    See the NPM font provider reference documentation for more details.

  • #​15548 5b8f573 Thanks @​florian-lefebvre! - Adds a new optional embeddedLangs prop to the <Code /> component to support languages beyond the primary lang

    This allows, for example, highlighting .vue files with a <script setup lang="tsx"> block correctly:

    ---
import { Code } from 'astro:components';

const code = `
<script setup lang="tsx">
const Text = ({ text }: { text: string }) => <div>{text}</div>;
</script>

<template>
  <Text text="hello world" />
</template>`;
---

<Code {code} lang="vue" embeddedLangs={['tsx']} />

    See the <Code /> component documentation for more details.

  • #​15483 7be3308 Thanks @​florian-lefebvre! - Adds streaming option to the createApp() function in the Adapter API, mirroring the same functionality available when creating a new App instance

    An adapter's createApp() function now accepts streaming (defaults to true) as an option. HTML streaming breaks a document into chunks to send over the network and render on the page in order. This normally results in visitors seeing your HTML as fast as possible but factors such as network conditions and waiting for data fetches can block page rendering.

    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 opt out of the default behavior by passing streaming: false to createApp():

    import { createApp } from 'astro/app/entrypoint';

const app = createApp({ streaming: false });

    See more about the createApp() function in the Adapter API reference.

Patch Changes

v6.0.0-beta.12

Compare Source

Major Changes

Configuration

📅 Schedule: 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 is behind base branch, or you tick the rebase/retry checkbox.

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

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

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

@renovate renovate bot force-pushed the renovate/astro-monorepo branch from b1e5ecb to c8f804a Compare November 29, 2025 17:12
@renovate renovate bot changed the title chore(deps): update dependency @astrojs/check to v0.9.5 chore(deps): update dependency @astrojs/check to v0.9.6 Nov 29, 2025
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from c8f804a to 4ded7cb Compare December 3, 2025 14:38
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 4ded7cb to 8baa932 Compare December 22, 2025 22:25
@changeset-bot
Copy link

changeset-bot bot commented Dec 22, 2025 •
edited
Loading

⚠️ No Changeset found

Latest commit: 109230d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot changed the title chore(deps): update dependency @astrojs/check to v0.9.6 chore(deps): update astro monorepo Dec 22, 2025
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from 8baa932 to 7fb9f41 Compare December 23, 2025 01:46
@renovate renovate bot changed the title chore(deps): update astro monorepo chore(deps): update dependency @astrojs/check to v0.9.6 Dec 23, 2025
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 2 times, most recently from 961691a to daa05b0 Compare January 23, 2026 17:02
@renovate renovate bot changed the title chore(deps): update dependency @astrojs/check to v0.9.6 chore(deps): update dependency @astrojs/check to v0.9.6 - autoclosed Jan 24, 2026
@renovate renovate bot closed this Jan 24, 2026
@renovate renovate bot deleted the renovate/astro-monorepo branch January 24, 2026 20:20
@renovate renovate bot changed the title chore(deps): update dependency @astrojs/check to v0.9.6 - autoclosed fix(deps): update astro monorepo Jan 30, 2026
@renovate renovate bot reopened this Jan 30, 2026
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 4 times, most recently from 4130f00 to e36decc Compare February 2, 2026 19:41
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 5 times, most recently from 407da6e to d7863bc Compare February 12, 2026 18:57
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 4 times, most recently from 153d422 to 2821f3d Compare February 20, 2026 18:38
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 2 times, most recently from cb018a7 to a664b95 Compare February 27, 2026 17:50
@renovate renovate bot force-pushed the renovate/astro-monorepo branch 3 times, most recently from a2938cf to a98e6b7 Compare March 5, 2026 17:22
@renovate renovate bot force-pushed the renovate/astro-monorepo branch from a98e6b7 to 109230d Compare March 7, 2026 17:52
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