-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Astro v6.0 #12322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Astro v6.0 #12322
Conversation
✅ Deploy Preview for astro-docs-2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Lunaria Status Overview🌕 This pull request will trigger status changes. Learn moreBy default, every PR changing files present in the Lunaria configuration's You can change this by adding one of the keywords present in the Tracked Files
Warnings reference
|
Co-authored-by: Sarah Rainsberger <[email protected]>
Co-authored-by: Sarah Rainsberger <[email protected]>
Co-authored-by: Sarah Rainsberger <[email protected]>
Co-authored-by: Matt Kane <[email protected]> Co-authored-by: Sarah Rainsberger <[email protected]>
Co-authored-by: Sarah Rainsberger <[email protected]>
Co-authored-by: Sarah Rainsberger <[email protected]>
Co-authored-by: Sarah Rainsberger <[email protected]>
Co-authored-by: Armand Philippot <[email protected]> Co-authored-by: Sarah Rainsberger <[email protected]>
Co-authored-by: Matt Kane <[email protected]> Co-authored-by: Junseong Park <[email protected]> Co-authored-by: Sarah Rainsberger <[email protected]>
Co-authored-by: Louis Escher <[email protected]> Co-authored-by: Sarah Rainsberger <[email protected]>
Co-authored-by: Sarah Rainsberger <[email protected]>
Co-authored-by: Sarah Rainsberger <[email protected]>
Co-authored-by: knj <[email protected]> Co-authored-by: Yan <[email protected]>
Co-authored-by: Yan <[email protected]> Co-authored-by: knj <[email protected]>
Co-authored-by: Chris Swithinbank <[email protected]> Co-authored-by: Yan <[email protected]> Co-authored-by: Sarah Rainsberger <[email protected]>
Co-authored-by: Florian Lefebvre <[email protected]> Co-authored-by: Armand Philippot <[email protected]>
…vior (#12639) Co-authored-by: Sarah Rainsberger <[email protected]> Co-authored-by: Florian Lefebvre <[email protected]> Co-authored-by: Armand Philippot <[email protected]>
Co-authored-by: Sarah Rainsberger <[email protected]>
| group('guides.upgrade.major', { | ||
| collapsed: true, | ||
| items: [ | ||
| 'guides/upgrade-to/v5', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if we typically do this later, but I think we shouldn't forget to add the v6 migration guide to the right sidebar group:
| 'guides/upgrade-to/v6', | |
| 'guides/upgrade-to/v5', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't apply some of these suggestions since GitHub thinks they are outdated, @trueberryless . Can you please instead make separate PRs to the v6 branch instead of suggestions here for the ones I can't commit? These become difficult to handle on GitHub and it is much easier to rely on separate PRs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, I'm gonna create another PR then, so GitHub behaves 👍
Co-authored-by: Florian Lefebvre <[email protected]> Co-authored-by: Sarah Rainsberger <[email protected]>
Co-authored-by: Armand Philippot <[email protected]> Co-authored-by: Matt Kane <[email protected]> Co-authored-by: Yan <[email protected]> Co-authored-by: HiDeoo <[email protected]> Co-authored-by: OliverSpeir <[email protected]>
Co-authored-by: HiDeoo <[email protected]>
Co-authored-by: Sarah Rainsberger <[email protected]>
Co-authored-by: Felix Schneider <[email protected]>
Co-authored-by: Armand Philippot <[email protected]> Co-authored-by: Sarah Rainsberger <[email protected]>
Co-authored-by: Sarah Rainsberger <[email protected]>
Co-authored-by: Armand Philippot <[email protected]> Co-authored-by: Sarah Rainsberger <[email protected]> Co-authored-by: Yan <[email protected]> Co-authored-by: florian-lefebvre <[email protected]>
The branch for your docs for all Astro v6.0 PRs! (Astro Milestone: https://github.com/withastro/astro/milestone/37)
Big changes (that people may still want to review even though they've been merged in) include:
Upgrade guide: https://deploy-preview-12322--astro-docs-2.netlify.app/en/guides/upgrade-to/v6/
Content Collections: Content Collections Guide,
astro:contentmodule reference, and Content Loader API reference including explaining the basic format/functions of loaders and how to build them.Breaking changes (additions, removals, deprecations, stablizings...)
File to edit: v6 upgrade page:
src/content/docs/en/guides/upgrade-to/v6.mdxUse v5 upgrade guide as an example of format:
src/content/docs/en/guides/upgrade-to/v5.mdxTemplate
(More guidance available in the Astro Docs Docs guide to breaking changes)
NB: Even if we decide to change up the format, e.g. organizing by topic vs by kind of change, or other options for easier scanning/readability, then at least providing the content in the same format from last year will give docs the information needed. We can move around/rearrange as needed.