-
Notifications
You must be signed in to change notification settings - Fork 146
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
chore: Forge v6 blog post #278
Conversation
2eda178
to
c61c2dc
Compare
c61c2dc
to
d708384
Compare
We should probably add a "Migrating from v5 to v6" section, just to outline the major changes people will need to look out for. |
I removed this section as per Erick's first comment- given that 1/30 of our users are using v5, and that the migration guide basically says "run the script, resolve any remaining conflicts in the config" it may not be valuable in the blog |
f5b703e
to
617855a
Compare
617855a
to
fc894c6
Compare
fc2b304
to
26f7668
Compare
26f7668
to
03c85fb
Compare
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.
Tentative ✅ - going to hold off approving until we're ready to merge (right after stable)
03c85fb
to
8fce9e4
Compare
7200c59
to
5a7bb5e
Compare
1202f14
to
01665d1
Compare
ff67c09
to
bf48d2e
Compare
bf48d2e
to
267553b
Compare
WOO 🍾 |
initial PR to get things going ahead of forge v6 release.
Questions/ areas of note