Eliminate manual steps in release process
Eliminate manual step reviewing peer dependencies during the release process - automate the process. We must maintain the V2 setup, where we update only the packages / deps that actually changed. Leave the manual review of the changeset PR, but update the dependencies before
Improving the release process is an ongoing task and will go through many iterations. Our top priority should be two tasks:
- re-adding the auto-creation of draft github releases (an appreciated time saver of the Alpha release flow)
- minimizing the manual review and update caused by unneeded changset alterations of peerDepenencies.
Peer dependencies update cannot be fully automated, because it requires insight into the changes
An intentional manual step was added to alert the release author to verify the the peer deps.
The author myst review the deps and add the label peer dependencies reviewed to confirm the action.
The remaining manual step that can be automated is the creation of a GitHub release. @kanej please let me know if you could dedicate some time to the effort before Christmas.