build(site): upgrade Astro to v7 - #8425
Conversation
…ee2665aa59b485ac2)
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
🔗 Linked repositories identifiedCodeRabbit considers these linked repositories for cross-repo context during reviews:
Included review availability: 5 reviews are currently available. Based on recent review activity, included reviews refill at 6 per hour. 📝 WalkthroughSummary by CodeRabbit
WalkthroughThe site package manifest adds Estimated code review effort: 1 (Trivial) | ~3 minutes Merge Risk: ⚪ Minimal · up to This PR upgrades Astro and related Markdown dependencies without any identified merge-blocking risk; it is merge-ready after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Comment |
commit: |
🔗 View agent run: https://app.netlify.com/projects/cli/agent-runs/6a843edee2665aa59b485ac2
🤖 Agent: Opencode (deepseek/deepseek-v4-pro)
💬 Prompt: Upgrade my Astro project to v7. Follow the migration guide at
https://docs.astro.build/en/guides/upgrade-to/v7/
✅ Result:
Summary
Upgraded the Astro project from v6 to v7 following the official migration guide.
What changed
astroupgraded from6.4.6to7.2.2@astrojs/starlightupgraded from0.39.3to0.41.7(0.40+ dropped support for Astro 6; 0.41+ requires Astro 7)@astrojs/markdown-remarkadded as an explicit dependency at7.2.2— required as a peer dependency by both Astro 7 and Starlight 0.41+ for the remark/rehype Markdown pipelineWhat was verified (no changes needed)
src/fetch.tsfile exists, so no conflict with the new reserved filenameastro:transitionsinternals (createAnimationScope,TRANSITION_*) were referencedgetContainerRenderer()imports from integration roots@astrojs/dbusage@astrojs/sitemapremained at3.7.3(already latest, sourced as a transitive dependency of Starlight)Build perf changes
Five cold builds (clearing
dist/between each) and five warm builds (no clearing) were run for both Astro v6.4.6 and Astro v7.2.2 on the same machine with identical source content.