Post Update Checklist is useful in ensuring that you haven't introduced any regressions to your code base after making sweeping code changes. You are asked to consider executing this checklist after every phase of the update process. It may not always be possible or feasible to execute the entire list, but after making significant changes to your code base, if necessary, update your unit tests, and execute the following checklist incrementally:

1. Build and smoke test your angular app
2. Commit your changes
3. With each commit, ensure that CI pipeline remains green
4. If making functional changes, it may be required to follow release-cycle procedures of your organization, which may include manual testing by a QA team
5. It is advisable to implement and deploy such changes one by one and deploy them to the production environment
6. Collect Performance data, as outlined in the following section

Committing your code after a category of changes will enable you to revert or cherry-pick further upgrade commits, if something goes wrong down the line.

For a variety of reasons, you may need to manually upgrade Angular, which is covered in the next section.