There have been unfortunate situations where upgrading to a new version of the Deploy/Release tooling has caused breaks/issues to arise that did not come up in our own regression/pre upgrade testing. But due to how coupled upgrades are to database table updates, it is nearly impossible to rollback without a huge amount of time dedicated to correcting those database changes.
We are hoping to have better support/options for major version upgrades so they are not as painful to revert. The enhancement/feature would help response team from affected developers using our tool and getting the tooling back to a previous working state faster.
by: Bryan G. | 6 days ago | Installation & Upgrades
Comments
Thanks for sharing this request - it’s very relevant feedback. Implementing more sophisticated rollbacks requires major changes to database upgrade handling and broader architectural updates. We are considering this as part of larger platform improvements over time. Our first target is to make upgrades smoother so teams encounter fewer issues during updates and have less need to roll back.