Force ng update or clean repository rerun for Angular upgrade recovery?

The goal is to choose a recovery method after a failed Angular upgrade when ng update aborts due to peer dependency conflicts. The decision must balance upgrade speed, long‑term stability, and the state of the local repository.

Using ng update with --force lets the command finish quickly, but it may install versions that are incompatible with Angular schematics or other libraries, potentially causing runtime errors that surface later. The alternative is to revert the failed update, resolve the conflicts (e.g., by upgrading the offending library), then rerun ng update without --force to obtain a clean dependency graph; this approach is safer but requires time to fix conflicts and assumes a clean git history or the ability to stash/commit local changes.

• Which strategy minimizes the risk of post‑upgrade runtime incompatibilities while keeping upgrade time acceptable?
• Under what circumstances is a forced update with --force considered an acceptable trade‑off?
• How does the presence of uncommitted local changes influence the feasibility of the clean‑rerun approach?