deps: bump astro from 6.3.7 to 7.1.1

[dependabot]

Bumps astro from 6.3.7 to 7.1.1.

Release notes

Sourced from astro's releases.

astro@7.1.1

Patch Changes

• #17399 4b03702 Thanks @​matthewp! - Fixes encoded request paths being routed incorrectly when using domain-based i18n

astro@7.1.0

Minor Changes

• #17302 5f4dc03 Thanks @​astrobot-houston! - Adds a new deferRender option to the glob() content loader

  When set to true, renderable entries (such as Markdown) are not rendered during content sync. Instead, rendering is deferred until the entry is actually rendered in a page, using the same on-demand path that .mdx files already use.

  This reduces memory usage during astro build for large collections whose rendered output is much larger than the source — for example, Markdown that uses heavy rehype plugins like rehype-katex. Such builds could previously run out of memory while storing the eagerly-rendered HTML for every entry.

  // src/content.config.ts
  import { defineCollection } from 'astro:content';
  import { glob } from 'astro/loaders';
  const docs = defineCollection({
  loader: glob({ pattern: '**/*.md', base: 'src/content/docs', deferRender: true }),
  });

  By default deferRender is false, preserving the existing behavior of rendering entries eagerly during sync so their rendered HTML can be cached across builds.

• #17296 30698a2 Thanks @​ematipico! - Adds a new experimental collectionStorage option for controlling how the content layer persists its data store

  By default, Astro serializes the entire content layer data store to a single file (.astro/data-store.json). For very large content collections, this file can grow large enough to hit platform file-size limits.

  Set experimental.collectionStorage: 'chunked' to instead split the data store across many smaller, content-addressed files inside a .astro/data-store/ directory, described by a manifest:

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  export default defineConfig({
  experimental: {
  collectionStorage: 'chunked',
  },
  });

  Because each part file is named by a hash of its contents, unchanged parts keep the same name across builds and are not rewritten, and identical parts are deduplicated. The default value is 'single-file', which preserves the current behavior.

• #17214 44c4989 Thanks @​ematipico! - Adds support for the more specific CSP directives script-src-elem, script-src-attr, style-src-elem, and style-src-attr through a new kind option.

  Previously, CSP was only scoped to generic script-src/style-src directives. Now each source or hash can be scoped to a narrower directive — for example, to allow inline style attributes (such as those from define:vars or Shiki) without loosening the policy for your <style> and <link> elements.

  Scoping sources and hashes in your config

... (truncated)

Changelog

Sourced from astro's changelog.

7.1.1

Patch Changes

• #17399 4b03702 Thanks @​matthewp! - Fixes encoded request paths being routed incorrectly when using domain-based i18n

7.1.0

Minor Changes

• #17302 5f4dc03 Thanks @​astrobot-houston! - Adds a new deferRender option to the glob() content loader

  When set to true, renderable entries (such as Markdown) are not rendered during content sync. Instead, rendering is deferred until the entry is actually rendered in a page, using the same on-demand path that .mdx files already use.

  This reduces memory usage during astro build for large collections whose rendered output is much larger than the source — for example, Markdown that uses heavy rehype plugins like rehype-katex. Such builds could previously run out of memory while storing the eagerly-rendered HTML for every entry.

  // src/content.config.ts
  import { defineCollection } from 'astro:content';
  import { glob } from 'astro/loaders';
  const docs = defineCollection({
  loader: glob({ pattern: '**/*.md', base: 'src/content/docs', deferRender: true }),
  });

  By default deferRender is false, preserving the existing behavior of rendering entries eagerly during sync so their rendered HTML can be cached across builds.

• #17296 30698a2 Thanks @​ematipico! - Adds a new experimental collectionStorage option for controlling how the content layer persists its data store

  By default, Astro serializes the entire content layer data store to a single file (.astro/data-store.json). For very large content collections, this file can grow large enough to hit platform file-size limits.

  Set experimental.collectionStorage: 'chunked' to instead split the data store across many smaller, content-addressed files inside a .astro/data-store/ directory, described by a manifest:

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  export default defineConfig({
  experimental: {
  collectionStorage: 'chunked',
  },
  });

  Because each part file is named by a hash of its contents, unchanged parts keep the same name across builds and are not rewritten, and identical parts are deduplicated. The default value is 'single-file', which preserves the current behavior.

• #17214 44c4989 Thanks @​ematipico! - Adds support for the more specific CSP directives script-src-elem, script-src-attr, style-src-elem, and style-src-attr through a new kind option.

  Previously, CSP was only scoped to generic script-src/style-src directives. Now each source or hash can be scoped to a narrower directive — for example, to allow inline style attributes (such as those from define:vars or Shiki) without loosening the policy for your <style> and <link> elements.

... (truncated)

Commits

• 91c645a [ci] release (#17403)
• 4b03702 Normalize domain-based i18n request paths consistently (#17399)
• fdd673c [ci] release (#17387)
• d9f99e1 Preserve CSP resource defaults for element directives (#17394)
• 092da56 Add more escaping for rendered content (#17393)
• 186a1e7 fix(logger): allows setting in updateConfig() (#17391)
• 4407483 fix(logger): use console API in JSON logger for cross-runtime compatibility...
• 16de021 feat(logger): allow passing entrypoint as URL (#17389)
• ed71eaf fix(logger): make AstroLoggerDestination not generic (#17390)
• 30698a2 feat: chunk data store (#17296)
• Additional commits viewable in compare view

[EricAndrechek]

Why this can't merge as-is

Astro 7 alone is peer-broken against the pinned Starlight:

• @astrojs/starlight@0.38.5 (what main resolves) peer-requires astro: ^6.0.0
• @astrojs/starlight@0.41.x peer-requires astro: ^7.0.2

So astro and Starlight have to move in the same commit. Dependabot can't escape this on its own — it won't propose a Starlight bump while astro is on 6, and it won't pull astro 7 into the Starlight PR — which is why this has sat here since 2026-07-21.

The same knot catches two entries in #439: starlight-image-zoom@0.15.0 and starlight-links-validator@0.25.2 both require @astrojs/starlight >= 0.41. Installed against 0.38.5 the docs build dies with:

[AstroUserError] The configured 'markdown.processor' is not supported by the starlight-image-zoom plugin.

Those two are held back in #439 and ride along here instead.

What this PR needs to become

One coordinated upgrade, verified locally (not yet pushed):

Package	From	To
astro	6.3.7	7.1.6
@astrojs/starlight	0.38.5	0.41.6
starlight-image-zoom	0.14.2	0.15.0
starlight-links-validator	0.24.1	0.25.2

Not 7.2.0 / 0.41.7: both were published inside the minimumReleaseAge: 10080 (7-day) supply-chain cooldown in pnpm-workspace.yaml, so pnpm install rejects them with ERR_PNPM_NO_MATURE_MATCHING_VERSION. 7.1.6 and 0.41.6 are the newest that clear the window.

No source changes were needed — every other integration declares a permissive peer range (@astrojs/starlight-tailwind, @wave-rf/starlight-llm-tools, @wave-rf/astro-themed-mermaid, @wave-rf/cloudflare-md-router) and all satisfy Astro 7 / Starlight 0.41 as-is.

One lockfile fix was required: rehype-katex and rehype-mermaid had a stale @types/hast@3.0.4 pinned while Astro 7's markdown chain resolves 3.0.5. Two copies make the Root types structurally incompatible and astro check rejects the rehypePlugins array. Both packages already declare @types/hast: ^3.0.0 and are at their latest versions, so pnpm dedupe collapses them to a single 3.0.5 — no override needed.

Verification

make build-docs clean: 21 pages, all internal links valid, 68 diagram PNGs rendered, pagefind index built.

Follow-up (not in this PR)

Astro 7 deprecates markdown.remarkPlugins / markdown.rehypePlugins / markdown.remarkRehype in favour of unified({...}) from @astrojs/markdown-remark. It's a warning today and the build is green, but it will break on Astro 8 — worth its own issue rather than widening this one.

[github-actions]

📚 Docs preview is live → https://53db01ae-wavehouse-docs.wave-rf.workers.dev

• Commit — 807d53f: deps: carry starlight 0.41 with the astro 7 upgrade
• Author — @EricAndrechek, Claude Opus 5 (1M context)
• Committed — 2026-08-10 15:25 (UTC-04:00)
• Deployed — 2026-08-10 15:29 EDT

[github-code-quality]

Code Coverage Overview

Languages: Go

Go

The overall coverage in commit 807d53f in the dependabot/npm_and_y... branch remains at 90%, unchanged from commit 4f599bd in the main branch.

Show a code coverage summary of the most impacted files.

File	main 4f599bd	dependabot/npm_and_y... 807d53f	+/-
cmd/wavehouse/main.go	70%	72%	+2%