When a customer goes to create a release, we display the current version number next to the text input. There is currently nothing preventing the user from creating a release with a version number less than the current one. We should validate the version number in javascript as the version number is inputted.
Users can draft releases. This makes it possible for a user to draft a release, r1, with version 1.1. Then create another release, r2, with version 1.2. If the user then activates r2, we need to prevent the user from releasing r1 because its version number is now outdated. To accomplish this, we should display a warning message on top of the outdated release and prevent the user from toggling the status to Active.
When a customer goes to create a release, we display the current version number next to the text input. There is currently nothing preventing the user from creating a release with a version number less than the current one. We should validate the version number in javascript as the version number is inputted.
Users can draft releases. This makes it possible for a user to draft a release, r1, with version 1.1. Then create another release, r2, with version 1.2. If the user then activates r2, we need to prevent the user from releasing r1 because its version number is now outdated. To accomplish this, we should display a warning message on top of the outdated release and prevent the user from toggling the status to Active.