bump to v12; API to estimated release date (#6808)

oxidecomputer · Oct 15, 2024 · 20220b8 · 20220b8
1 parent 99e72c7
commit 20220b8
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git a/dev-tools/openapi-manager/src/spec.rs b/dev-tools/openapi-manager/src/spec.rs
@@ -93,7 +93,7 @@ pub fn all_apis() -> Vec<ApiSpec> {
         },
         ApiSpec {
             title: "Oxide Region API",
-            version: "20241009.0",
+            version: "20241204.0",
             description: "API for interacting with the Oxide control plane",
             boundary: ApiBoundary::External,
             api_description:

diff --git a/dev-tools/releng/src/main.rs b/dev-tools/releng/src/main.rs
@@ -41,7 +41,7 @@ use crate::job::Jobs;
 /// to as "v8", "version 8", or "release 8" to customers). The use of semantic
 /// versioning is mostly to hedge for perhaps wanting something more granular in
 /// the future.
-const BASE_VERSION: Version = Version::new(11, 0, 0);
+const BASE_VERSION: Version = Version::new(12, 0, 0);
 
 const RETRY_ATTEMPTS: usize = 3;
 

diff --git a/nexus/external-api/src/lib.rs b/nexus/external-api/src/lib.rs
@@ -23,7 +23,7 @@ use omicron_common::api::external::{
 use openapi_manager_types::ValidationContext;
 use openapiv3::OpenAPI;
 
-pub const API_VERSION: &str = "20241009.0";
+pub const API_VERSION: &str = "20241204.0";
 
 // API ENDPOINT FUNCTION NAMING CONVENTIONS
 //

diff --git a/openapi/nexus.json b/openapi/nexus.json
@@ -7,7 +7,7 @@
       "url": "https://oxide.computer",
       "email": "api@oxide.computer"
     },
-    "version": "20241009.0"
+    "version": "20241204.0"
   },
   "paths": {
     "/device/auth": {