-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Make the update guide evergreen #33034
Conversation
Thanks for your pull request! The title of your pull request does not follow our editorial rules. Could you have a look?
|
🙈 The PR is closed and the preview is expired. |
cac97de
to
96f1d6f
Compare
@aloubyansky, would you review/approve this MR? |
96f1d6f
to
f4c318c
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.
Looks good to me. @gsmet wdyt?
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.
Added a comment about the file name.
The other comment can be addressed now or later.
e8418c9
to
1dad24f
Compare
1dad24f
to
8f98a46
Compare
Thanks! Could you create a PR against the website to install a redirect? I will merge it when I release this change. Thanks! |
I wonder how we can make the update guide evergreen so it doesn't need to be updated.
Here, I've removed almost all references to specific versions, or suggested using the "latest version".
I believe the user can omit
--stream=3.0
from thequarkus update --stream=3.0
command. The command seems to default to the latest version, too.Doc preview link: https://quarkus-pr-main-33034-preview.surge.sh/version/main/guides/update-quarkus
Compare with the current published guide: https://quarkus.io/guides/update-to-quarkus-3