bump to v16; API version to planned release date (#8574)

Author: iliana

dev-tools/openapi-manager/src/omicron.rs

@@ -110,7 +110,7 @@ pub fn all_apis() -> Vec<ManagedApiConfig> {
         ManagedApiConfig {
             title: "Oxide Region API",
             versions: Versions::new_lockstep(semver::Version::new(
-                20250604, 0, 0,
+                20250730, 0, 0,
             )),
             description: "API for interacting with the Oxide control plane",
             boundary: ApiBoundary::External,

dev-tools/releng/src/main.rs

@@ -46,7 +46,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(15, 0, 0);
+const BASE_VERSION: Version = Version::new(16, 0, 0);
 
 const RETRY_ATTEMPTS: usize = 3;
 

nexus/external-api/src/lib.rs

@@ -26,7 +26,7 @@ use omicron_common::api::external::{
 use openapi_manager_types::ValidationContext;
 use openapiv3::OpenAPI;
 
-pub const API_VERSION: &str = "20250604.0.0";
+pub const API_VERSION: &str = "20250730.0.0";
 
 const MIB: usize = 1024 * 1024;
 const GIB: usize = 1024 * MIB;

openapi/nexus.json

@@ -7,7 +7,7 @@
       "url": "https://oxide.computer",
       "email": "api@oxide.computer"
     },
-    "version": "20250604.0.0"
+    "version": "20250730.0.0"
   },
   "paths": {
     "/device/auth": {