Skip to content

deps: upgrade to Astro 7.1 #39

Description

@maehr

Summary

Astro 7.1 is out (https://astro.build/blog/astro-710/). It is a minor, backwards-compatible release on the Astro 7 line — unlike the 6→7 jump tracked in #20, no breaking changes are expected. We currently run astro@7.0.6 / @astrojs/starlight@0.41.3.

What 7.1 brings (highlights)

  • Finer-grained CSP directives (script-src-elem/attr, style-src-elem/attr).
  • format function on paginate() for customizing generated URLs.
  • --ignore-lock to run multiple dev servers for one project.
  • deferRender on content collections — defers rendering until needed instead of caching on sync.
  • Experimental experimental.collectionStorage: "chunked" — splits the data store at 10MB.
  • Logger API improvements (AstroRuntimeLogger).

Why it matters here

deferRender and chunked collection storage are directly relevant as the registry grows toward millions of references (see ROADMAP "Later"): they address large-collection memory and the 10MB data-store ceiling.

Checklist

  • Confirm all Starlight plugins in astro.config.mjs are compatible with 7.1 (they target astro >=7; starlight-llms-txt was the Upgrade to Starlight 0.41 / Astro 7 (blocked on starlight-llms-txt) #20 blocker — verify its current floor).
  • Bump astro to ^7.1.x; refresh other deps as needed.
  • Run npm run verify (format:check + astro check + build) and npm run check:links.
  • Sanity-check /llms.txt, /api/ OpenAPI pages, mermaid diagrams, blog, and the /id/* record pages.
  • Evaluate adopting deferRender / experimental.collectionStorage: "chunked" for the registry data (follow-up, optional).

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    addressed-in-v0.1.0Addressed in the v0.1.0 release (PR #4)dependenciesPull requests that update a dependency file

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions