Updated release automation spec to account for the case when the prev…

…ious release is newer than the new release on github and osf.
Big-Life-Lab · Mar 20, 2023 · 1ebdd2c · 1ebdd2c
1 parent 767556f
commit 1ebdd2c
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/specs/release-automation/release-automation-specs.qmd b/specs/release-automation/release-automation-specs.qmd
@@ -65,8 +65,8 @@ There are three states that need to handled when deplying the file to OSF,
 
 1. When there are no release files on OSF. This means that this is the first release of the dictionary and all the files should be created and put in their correct location.
 2. When there is a previous release on OSF whose version is not the same as the new release. 
-    All the old files need to be moved to a sub folder within an archive folder. The name of the sub folder should be the previous release version. Within the sub folder, the previous release files should be placed in their old paths. 
-    From there, the new files should created and put in their correct location.
+    2.1. If the previous release is newer than the new release, then an error should be thrown and the entire process should stop.
+    2.2: Otherwise, all the old files need to be moved to a sub folder within an archive folder. The name of the sub folder should be the previous release version. Within the sub folder, the previous release files should be placed in their old paths. From there, the new files should created and put in their correct location.
 3. When there is a previous release on OSF whose version is the same as the new release.
     All the old files should be deleted.
     The new files should be created and put in their correct location.
@@ -83,8 +83,8 @@ Similar to the OSF deployment feature, the following two states will need to be
     A commit should be made with the new files called `[BOT] release-{version}`
     A PR should be made from the new branch into `dev`. The PR should be called `[BOT] Release {version}`
 2. When there is a release version on GitHub 
-    All the old files need to be deleted
-    The same steps as the first state need to be followed
+    2.1. If the previous release is newer than the new release, then an error should be thrown and the entire process should stop.
+    2.2: Otherwise, all the old files need to be deleted. The same steps as the first state need to be followed
 
 Finally, for every new release any existing release branches need to be deleted and their PRs need to be closed.