Does ROS 2 provide an automatic rollback command after a failed package upgrade?

Goal

Determine whether ROS 2 includes a built‑in command that can automatically revert a workspace to the previously installed package versions after a failed upgrade, without requiring manual version‑control steps.

Constraints arise because ROS 2 upgrades are performed with colcon build (or catkin_make for ROS 1) and dependencies are updated via rosdep. Overlay workspaces let developers test new versions alongside the installed ones, but they do not provide an automatic rollback path when the build fails, and there is no documented ROS‑wide mechanism that records prior package versions for bulk restoration.

Uncertainty remains about whether the rosdistro metadata or release repositories could be leveraged to create such a rollback tool, or if developers must rely on external practices like committing source changes and rebuilding from a known good commit.

1. Does ROS 2 currently provide a command that automatically rolls back all upgraded packages to their former versions after a failed colcon build?
2. If no such command exists, what are the recommended, version‑control‑free strategies for achieving a safe workspace rollback?