Apply doc change from starkware-libs#183

FabijanC · Dec 7, 2023 · f0de5e2 · f0de5e2
1 parent 3e3c083
commit f0de5e2
Showing 1 changed file with 5 additions and 5 deletions.
diff --git a/api/release.md b/api/release.md
@@ -37,17 +37,17 @@ Releases follow [semantic versioning](https://semver.org) for version tags.
 We use `rc`_i_ ( i = 1,2,...) suffix to qualify different release candidates.
 No suffix to a version means it's the recommendation version.
 
+## Different Specification Documents
+
+A release number is relevant to all API specification documents at the same time. In other words, they are all considered a single document.
+Some parts of the API, e.g. the trace API, are considered optional. Still, they affect and adhere to the semantic version of the release.
+
 When updating the specification version, change the `"version"` property in all of the specification files. Also update the version in `package*.json` files by running:
 
 ```
 npm version <VERSION> --no-git-tag-version
 ```
 
-## Different Specification Documents
-
-A release number is relevant to all API specification documents at the same time. In other words, they are all considered a single document.
-Some parts of the API, e.g. the trace API, are considered optional. Still, they affect and adhere to the semantic version of the release.
-
 ## Technical Implementation
 
 We use github releases on this repo to publish releases.