-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
docs: re-arrange and clarify migration docs #15575
Conversation
@@ -2,7 +2,13 @@ | |||
sidebar_position: 1 | |||
--- | |||
|
|||
# Pre-Upgrade Handling | |||
# Migrations |
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.
Put the migrations to perform by a chain under building-apps
, what do you think?
Then the migration, more SDK related is under the migration section.
I think it makes sense, but curious about your input.
|
||
## Add SDK migration documentation | ||
cp -r ../UPGRADING.md ./docs/migrations/02-upgrading.md |
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.
This will render the UPGRADING.md directly on the website.
@Mergifyio backport release/v0.47.x |
✅ Backports have been created
|
backporting to make it coherent. |
(cherry picked from commit 2262199) # Conflicts: # UPGRADING.md # docs/.gitignore # docs/post.sh # docs/pre.sh
…osmos#15584) Co-authored-by: Julien Robert <julien@rbrt.fr>
Description
Attempts to re-arrange and clarify migration docs.
Comes from the params discussions.
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
to the type prefix if API or client breaking changeCHANGELOG.md
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
!
in the type prefix if API or client breaking change