chore: upgrade Astro to v6.1.2#630
Closed
davlgd wants to merge 1 commit into
Closed
Conversation
Owner
|
Thanks for putting this together. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Upgrades Astro from
5.16.6to6.1.2, following the official Astro v6 Migration Guide.Dependency bumps
astro^5.16.6^6.1.2@astrojs/rss^4.0.14^4.0.18/rss.xmlwithz.function(...).returns is not a function)@astrojs/sitemap^3.6.0^3.7.2@shikijs/transformers^3.20.0^4.0.2Configuration changes
astro.config.tsfontsout ofexperimental— the Fonts API is now stable in v6.experimental.preserveScriptOrder— preserved source order is the new default in v6, so the flag has been removed from the experimental API; dropping it keeps the current behavior.@ts-ignoreon thetailwindcss()Vite plugin: the upstream issue (withastro/astro#14030) is resolved with Vite 7 support in Astro 6.src/content.config.tszre-export fromastro:contentwith an import fromastro/zod, as recommended by the migration guide.Types of changes
Checklist
Further comments
Build verification
With local Node.js 24 LTS
Breaking changes reviewed
tailwindcss()works without the previous@ts-ignoreworkaround.@astrojs/rssand@astrojs/sitemapbumped to versions that already use Zod 4.@shikijs/transformersaligned to v4.Astro.glob()/<ViewTransitions />removed — not used in source code.Out of scope (suggested follow-ups)
These are stable v6 capabilities that AstroPaper could benefit from but are intentionally not included in this PR to keep the migration reviewable:
security.csp— built-in Content Security Policy with automatic hashing of bundled scripts/styles. A natural fit for a blog template; would need a small allowlist if Giscus / analytics are enabled.prerenderConflictBehavior: "error"— fails the build when two routes generate the same prerendered URL (e.g. a post slug colliding with a tag).Related documentation
Related Issue
Closes: #626