Skip to content

chore(deps): update astro monorepo (major) - #112

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

chore(deps): update astro monorepo (major)#112
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-astro-monorepo

Conversation

@renovate

@renovate renovate Bot commented Mar 10, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@astrojs/netlify (source) ^6.4.0 → ^8.2.3 age confidence
astro (source) ^4.14.0 || ^5.0.0 → ^4.14.0 || ^5.0.0 || ^7.0.0 age confidence
astro (source) ^5.10.1 → ^7.2.4 age confidence

Release Notes

withastro/astro (@​astrojs/netlify)

v8.2.3

Compare Source

Patch Changes

v8.2.2

Compare Source

Patch Changes

v8.2.1

Compare Source

Patch Changes

v8.2.0

Compare Source

Minor Changes
  • #​16871 90c98ae Thanks @​adamchal! - When session: false is set in astro.config, the adapter no longer auto-wires the Netlify Blobs session driver. Combined with the matching astro change, this lets the session runtime tree-shake out of the function bundle.
Patch Changes

v8.1.3

Compare Source

Patch Changes

v8.1.2

Compare Source

Patch Changes

  • #​17368 ee74c28 Thanks @​matthewp! - Fixes the generated Netlify Image CDN remote_images patterns so that regex metacharacters (such as .) in image.remotePatterns (hostname, pathname) and image.domains are matched literally instead of behaving like wildcards. This makes the generated patterns consistent with how Astro matches these values elsewhere.

  • Updated dependencies []:

v8.1.1

Compare Source

Patch Changes

v8.1.0

Compare Source

Minor Changes

  • #​17245 f56d9e7 Thanks @​astrobot-houston! - Adds edgeFunctions to the devFeatures adapter option, allowing users to disable Netlify Edge Function emulation during astro dev

    Some npm packages that access the filesystem at initialization (e.g. node-html-parser) fail inside the edge function sandbox with "Reading or writing files with Edge Functions is not supported yet." You can now disable edge function emulation to avoid this error:

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

export default defineConfig({
  adapter: netlify({
    devFeatures: {
      edgeFunctions: false,
    },
  }),
});

    Edge functions will still work in production builds and via netlify dev.

Patch Changes

v8.0.0

Compare Source

Major Changes
Minor Changes
Setup

Import cacheNetlify() from @astrojs/netlify/cache and set it as your cache provider:

import { defineConfig } from 'astro/config';
import netlify from '@astrojs/netlify';
import { cacheNetlify } from '@astrojs/netlify/cache';

export default defineConfig({
  adapter: netlify(),
  cache: {
    provider: cacheNetlify(),
  },
});
Caching responses

Use Astro.cache.set() in your pages and API routes to cache responses on Netlify's edge network. The provider uses Netlify's durable cache so cached responses are shared across all edge nodes, reducing function invocations.

---
Astro.cache.set({ maxAge: 300, tags: ['products'] });
const data = await fetchProducts();
---

<ProductList items={data} />

You can also set cache rules for groups of routes in your config:

cache: { provider: cacheNetlify() },
routeRules: {
  '/products/[...slug]': { maxAge: 3600, tags: ['products'] },
  '/api/[...path]': { maxAge: 60, swr: 600 },
},
Invalidation

Purge cached responses by tag or path from any API route or server endpoint:

// src/pages/api/purge.ts
export async function POST({ request, cache }) {
  await cache.invalidate({ tags: ['products'] });
  return new Response('Purged');
}

// Path-based invalidation
await cache.invalidate({ path: '/products/123' });

Both tag-based and path-based invalidation are supported.

Patch Changes

v7.0.13

Compare Source

Patch Changes

v7.0.12

Compare Source

Patch Changes

v7.0.11

Compare Source

Patch Changes

v7.0.10

Compare Source

Patch Changes

v7.0.9

Compare Source

Patch Changes

v7.0.8

Compare Source

Patch Changes

v7.0.7

Compare Source

Patch Changes

v7.0.6

Compare Source

Patch Changes

v7.0.5

Compare Source

Patch Changes

v7.0.4

Compare Source

Patch Changes

v7.0.3

Compare Source

Patch Changes

v7.0.2

Patch Changes

v7.0.1

Patch Changes

v7.0.0

Compare Source

Major Changes
Minor Changes

  • #​15258 d339a18 Thanks @​ematipico! - Stabilizes the adapter feature experimentalStatiHeaders. If you were using this feature in any of the supported adapters, you'll need to change the name of the flag:

    export default defineConfig({
  adapter: netlify({
-    experimentalStaticHeaders: true
+    staticHeaders: true
  })
})

  • #​15809 94b4a46 Thanks @​Princesseuh! - Adds support for the fit option to the image service

  • #​15495 5b99e90 Thanks @​leekeh! - Adds new middlewareMode adapter feature and deprecates edgeMiddleware option

    The edgeMiddleware option is now deprecated and will be removed in a future major release, so users should transition to using the new middlewareMode feature as soon as possible.

    export default defineConfig({
  adapter: netlify({
-    edgeMiddleware: true
+    middlewareMode: 'edge'
  })
})

  • #​15006 f361730 Thanks @​florian-lefebvre! - Adds new session driver object shape

    For greater flexibility and improved consistency with other Astro code, session drivers are now specified as an object:

    -import { defineConfig } from 'astro/config'
+import { defineConfig, sessionDrivers } from 'astro/config'

export default defineConfig({
  session: {
-    driver: 'redis',
-    options: {
-      url: process.env.REDIS_URL
-    },
+    driver: sessionDrivers.redis({
+      url: process.env.REDIS_URL
+    }),
  }
})

    Specifying the session driver as a string has been deprecated, but will continue to work until this feature is removed completely in a future major version. The object shape is the current recommended and documented way to configure a session driver.

  • #​15413 736216b Thanks @​florian-lefebvre! - Updates the implementation to use the new Adapter API

  • #​14946 95c40f7 Thanks @​ematipico! - Removes the experimental.csp flag and replaces it with a new configuration option security.csp - (v6 upgrade guidance)

Patch Changes

  • #​15187 bbb5811 Thanks @​matthewp! - Update to Astro 6 beta

  • #​15781 2de969d Thanks @​ematipico! - Adds a new clientAddress option to the createContext() function

    Providing this value gives adapter and middleware authors explicit control over the client IP address. When not provided, accessing clientAddress throws an error consistent with other contexts where it is not set by the adapter.

    Additionally, both of the official Netlify and Vercel adapters have been updated to provide this information in their edge middleware.

    import { createContext } from 'astro/middleware';

createContext({
  clientAddress: context.headers.get('x-real-ip'),
});

  • #​15665 52a7efd Thanks @​matthewp! - Fixes builds that were failing with "Entry module cannot be external" error when using the Netlify adapter

    This error was preventing sites from building after recent internal changes. Your builds should now work as expected without any changes to your code.

  • #​15679 19ba822 Thanks @​matthewp! - Fixes server-rendered routes returning 404 errors

    A configuration error in the build output prevented Netlify from correctly routing requests to server-rendered pages, causing them to return 404 errors. This fix ensures that all server routes are properly handled by the Netlify SSR function.

  • #​15809 94b4a46 Thanks @​Princesseuh! - Fixes the image CDN being used in development despite being disabled in certain cases

  • #​15460 ee7e53f Thanks @​florian-lefebvre! - Updates to use the new Adapter API

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

  • #​15461 9f21b24 Thanks @​florian-lefebvre! - Updates to new Adapter API introduced in v6

  • Updated dependencies [4ebc1e3, 4e7f3e8, a164c77, cf6ea6b, a18d727, 240c317, 745e632]:

v6.6.5

Compare Source

Patch Changes

v6.6.4

Compare Source

Patch Changes

v6.6.3

Compare Source

Patch Changes

v6.6.2

Compare Source

Patch Changes

v6.6.1

Compare Source

Patch Changes

v6.6.0

Compare Source

Minor Changes

  • #​14543 9b3241d Thanks @​matthewp! - Enables Netlify's skew protection feature for Astro sites deployed on Netlify. Skew protection ensures that your site's client and server versions stay synchronized during deployments, preventing issues where users might load assets from a newer deployment while the server is still running the older version.

    When you deploy to Netlify, the deployment ID is now automatically included in both asset requests and API calls, allowing Netlify to serve the correct version to every user. These are set for built-in features (Actions, View Transitions, Server Islands, Prefetch). If you are making your own fetch requests to your site, you can include the header manually using the DEPLOY_ID environment variable:

    const response = await fetch('/api/endpoint', {
  headers: {
    'X-Netlify-Deploy-ID': import.meta.env.DEPLOY_ID,
  },
});
Patch Changes

v6.5.13

Compare Source

Patch Changes

v6.5.12

Compare Source

Patch Changes

v6.5.11

Compare Source

Patch Changes

v6.5.10

Compare Source

Patch Changes

v6.5.9

Compare Source

Patch Changes

v6.5.8

Compare Source

Patch Changes

v6.5.7

Compare Source

Patch Changes

v6.5.6

Compare Source

Patch Changes
  • #​14175 1e1cef0 Thanks @​ematipico! - Fixes a bug where the adapter would cause a runtime error when calling astro build in CI environments.

v6.5.5

Compare Source

Patch Changes

v6.5.4

Compare Source

Patch Changes

v6.5.3

Compare Source

Patch Changes

v6.5.2

Compare Source

Patch Changes

v6.5.1

Compare Source

Patch Changes

v6.5.0

Compare Source

Minor Changes

This is an implementation update that does not require any change to your project code, but means that astro dev will run with an environment closer to a production deploy on Netlify. This brings several benefits you'll now notice working in dev mode!

For example, your project running in development mode will now use local versions of the Netlify Image CDN for images, and a local Blobs server for sessions. It will also populate your environment with the variables from your linked Netlify site.

While not required for fully static, prerendered web sites, you may still wish to add this for the additional benefits of now working in a dev environment closer to your Netlify production deploy, as well as to take advantage of Netlify-exclusive features such as the Netlify Image CDN.

Patch Changes

v6.4.1

Compare Source

Patch Changes
withastro/astro (astro)

v7.2.4

Compare Source

Patch Changes

v7.2.3

Compare Source

Patch Changes

  • #​17724 97140b2 Thanks @​ematipico! - Fixes an issue where Astro could run out of memory when experimental.collectionStorage is set to chunked and there are multiple concurrent updates to the same collection.

  • #​17636 51723b1 Thanks @​matthewp! - Fixes the dev server sometimes matching against stale routes after pages were added, removed, or renamed, requiring a dev server restart to pick up the change

  • #​17636 51723b1 Thanks @​matthewp! - Fixes the composable request helpers (astro/fetch) throwing an error when used on a request that had been rewritten with Astro.rewrite() or next()

  • #​17636 51723b1 Thanks @​matthewp! - Refactors Astro's internal server-side request handling. This is an internal change: all documented public APIs, including App and NodeApp, keep their existing signatures and behavior.

    The undocumented internal app.pipeline property and the AppPipeline export from astro/app have been removed. Adapters that used app.pipeline.getLogger() to wait for the configured log destination can call the new app.getLogger() instead.

    As a result of this refactor, new FetchState(request) from astro/fetch now works anywhere inside a built Astro server — including custom src/fetch.ts entrypoints — without the request needing to first pass through app.render(). Previously this threw an error, breaking patterns like the Cloudflare adapter's advanced custom-worker setup.

  • #​17723 c3b9aed Thanks @​florian-lefebvre! - Fixes a link in font providers JSDoc annotations

  • #​17699 e28d227 Thanks @​ArmandPhilippot! - Fixes several documentation issues related to the JSDoc for configuration options.

    • When hovering over the server and fonts options, the JSDoc for the nested options was displayed instead of the JSDoc for the top-level property.
    • Two i18n configuration options were being used incorrectly in the examples.
    • The indentation of some code blocks was broken on hover.

  • #​17572 2066f39 Thanks @​matthewp! - Fixes a crash when a request arrives with a malformed port in the Host header (for example example.com:65536 or example.com:8080:8080). Such a host made the constructed request URL invalid, and the fallback that was meant to recover reused the same invalid host and threw again. The request URL now degrades to a host the server controls when the incoming host cannot be parsed, so the request is handled instead of erroring.

  • #​17685 9f15609 Thanks @​astrobot-houston! - Fixes a dev server error where an SSR full reload triggered by a third-party Vite plugin (such as @tailwindcss/vite) could fail with Failed to load url astro:server-app.js

  • #​17636 51723b1 Thanks @​matthewp! - Improves error handling for custom log destinations. When the configured logger fails to load, Astro now reports the error and continues with the default console logger instead of failing the first request.

  • #​17631 cf29bec Thanks @​matthewp! - Fixes getCollection() and getEntry() throwing DataCloneError when a collection schema transform returns a Temporal.PlainDate or other class instance.

  • Updated dependencies [8c193f6]:

v7.2.2

Compare Source

Patch Changes

  • #​17611 9bc3207 Thanks @​thelazylamaGit! - Fixes component styles rendered from content entries remaining stale until a second save when an adapter uses Astro's fallback development environment

  • #​17634 2267eee Thanks @​astrobot-houston! - Fixes incremental builds dropping optimized images for cached pages when using a collectStaticImages prerenderer (e.g. @astrojs/cloudflare with compile-time image optimization)

  • #​17650 4cdf128 Thanks @​astrobot-houston! - Fixes intermittent ImageNotFound errors during build on projects with many images. The build now limits concurrent image file reads to avoid exhausting OS file descriptors (EMFILE) and retries transient I/O errors with backoff. Non-transient errors are no longer silently swallowed.

  • #​17683 2378221 Thanks @​astrobot-houston! - Fixes prerenderConflictBehavior not applying to content collection duplicate ID warnings in the glob() and file() loaders. Setting it to 'error' now throws during content sync, and 'ignore' suppresses the warning.

  • #​17659 90c6ea4 Thanks @​astrobot-houston! - Fixes the Fonts API breaking experimental.incrementalBuild caching by embedding a build-local, randomly-assigned server port in generated code used for the dependency hash

  • #​17630 fd1d9ee Thanks @​ericclemmons! - Fixes incremental builds becoming prohibitively slow for sites with many pages or content entries that share a large dependency graph.

  • #​17690 93beecc Thanks @​NgoQuocViet2001! - Prevents files in directories whose names start with pages from being treated as page routes

  • #​17671 09f0dc7 Thanks @​tarikermis! - Fixes astro dev refusing to start after a Docker container restart when an unrelated process reuses the PID from a persisted lock file. Astro now checks the process command across platforms, so stale

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR 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.

@netlify

netlify Bot commented Mar 10, 2026 •
edited
Loading

Copy link
Copy Markdown

❌ Deploy Preview for astro-loaders failed. Why did it fail? →

Name Link
🔨 Latest commit 5a2d006
🔍 Latest deploy log https://app.netlify.com/projects/astro-loaders/deploys/6a89dc1a79db3c000889a477

@changeset-bot

changeset-bot Bot commented Mar 10, 2026 •
edited
Loading

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 5a2d006

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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 force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from 95b40bf to 214f844 Compare March 10, 2026 17:17
@renovate renovate Bot changed the title chore(deps): update astro monorepo (major) chore(deps): update peerdependency astro to v6 Mar 10, 2026
@renovate
renovate Bot force-pushed the renovate/major-astro-monorepo branch from 214f844 to 61e28bf Compare March 10, 2026 20:51
@renovate renovate Bot changed the title chore(deps): update peerdependency astro to v6 chore(deps): update astro monorepo (major) Mar 10, 2026
@renovate
renovate Bot force-pushed the renovate/major-astro-monorepo branch from 61e28bf to bf86ece Compare March 14, 2026 12:59
@kydecker kydecker mentioned this pull request Mar 14, 2026
Open
@renovate
renovate Bot force-pushed the renovate/major-astro-monorepo branch 4 times, most recently from f85a829 to e875998 Compare March 20, 2026 18:36
@renovate
renovate Bot force-pushed the renovate/major-astro-monorepo branch 5 times, most recently from 7f02bfb to 9196ead Compare April 1, 2026 23:35
@renovate
renovate Bot force-pushed the renovate/major-astro-monorepo branch 2 times, most recently from e1c5452 to e0bcf42 Compare April 8, 2026 20:31
@renovate
renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 0c6d800 to 8adc768 Compare April 18, 2026 13:16
@renovate
renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 7be7d67 to f6c297d Compare April 29, 2026 13:40
@renovate
renovate Bot force-pushed the renovate/major-astro-monorepo branch 4 times, most recently from 239de2b to cd04050 Compare May 7, 2026 06:09
@renovate
renovate Bot force-pushed the renovate/major-astro-monorepo branch 5 times, most recently from 6e1c986 to 5241934 Compare June 1, 2026 16:54
@renovate
renovate Bot force-pushed the renovate/major-astro-monorepo branch 5 times, most recently from 9b0c810 to 8d9ffb7 Compare June 12, 2026 16:34
@renovate
renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 59ef2eb to 9fd79da Compare June 20, 2026 16:39
@renovate
renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from 6472b65 to e42eb64 Compare June 28, 2026 17:39
@renovate
renovate Bot force-pushed the renovate/major-astro-monorepo branch 3 times, most recently from e9dd208 to 33e567e Compare July 5, 2026 21:42
@renovate
renovate Bot force-pushed the renovate/major-astro-monorepo branch 4 times, most recently from 1946e1f to 0c755eb Compare July 17, 2026 00:20
@renovate
renovate Bot force-pushed the renovate/major-astro-monorepo branch 5 times, most recently from 9ea6b3e to ee0ad9a Compare July 24, 2026 17:56
@renovate
renovate Bot force-pushed the renovate/major-astro-monorepo branch from ee0ad9a to 3ef8d5f Compare July 30, 2026 18:56
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