1. On the Editor tab, the changed node starts showing the MODIFIED mark: that is how the editor shows what changed since the last save
2. The red dot next to the save icon means there are pending changes: click it to open the version save
3. The Save new version screen opens with Version title, Version description and Change type. Fill in the Version title, which is what identifies the change in the history
4. In Version description, spell out what changed for your team. The field is optional and takes formatted text
5. Change type comes pre-selected from what the system detected in the flow, and the bottom bar shows the Current version and the calculated number
6. There are three types: Patch for fixes, New features for additions and Breaking changes for what changes how executions behave. In this example we will use Breaking changes
7. When you switch the type, the badge goes from MINOR to MAJOR and the number moves up a level. Confirm on the button, which shows the new version number
8. The success message confirms the version was saved, and you stay on the same page with the flow open
9. The Versions tab shows the history, with number, title, description, date and the node count of each version