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: document ng update support guarantees
#44142
Conversation
LGTM for content, though one of the tech writers should weigh in on structure
Did a rewrite of your second paragraph to try to help clarify the meaning. Let me know what you think.
Looking good! A few minor changes. Some details as to why:
- Words like "simply" can be construed as condescending and are usually unnecessary anyway.
- Made the steps to update across multiple versions into a procedure to make it easier to read (and harder to skip. :) )
|
This PR was merged into the repository by commit 83bbbd3. |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
Other information
This adds explicit documentation about official support for
ng update, which is a bit awkward since it upgrades between two versions. It specifically calls out two aspects:ng updatecan only update across one major version at a time. The CLI should enforce this at run time, but it's good to document this more officially anyways.The text was updated successfully, but these errors were encountered: