Add Coming Soon and release support

docs.openc3.com/docs/guides/mcp-server.md

@@ -48,12 +48,14 @@ Then start claude and run the following to authenticate:
 `/mcp`
 
 ## Disabling the MCP Server
-<span class="badge badge--secondary since-right">Since 7.3.0</span>
-To disable the MCP Server entirely, set the following environment variable in the `.env` file at the root of your COSMOS Enterprise project and restart COSMOS:
+
+<span class="badge badge--secondary since-right">Since _Coming Soon_</span>
+To disable the MCP Server entirely, set the following environment variable in
+the `.env` file at the root of your COSMOS Enterprise project and restart
+COSMOS:
 
 ```
 OPENC3_MCP_DISABLED=true
 ```
 
 This prevents the MCP Server process from starting, so nothing listens at `/mcp`. Note that the Built-In AI Interface uses the MCP Server for all of its COSMOS interactions, so disabling the MCP Server also prevents the AI Interface from reading telemetry, sending commands, or running scripts. Remove the variable and restart COSMOS to re-enable.
-

docs.openc3.com/docs/guides/scripting-api.md

@@ -4947,7 +4947,7 @@ set_limits_set("DEFAULT")
 
 ### delete_limits_set
 
-<span class="badge badge--secondary since-heading">Since 7.3.0</span>
+<span class="badge badge--secondary since-heading">Since _Coming Soon_</span>
 
 Deletes a limits set and removes it from all telemetry items. The DEFAULT limits set and the currently active limits set cannot be deleted. Use [set_limits_set](#set_limits_set) to change the active set before deleting it. Use [get_limits_sets](#get_limits_sets) to get the available limit set names.
 
@@ -5152,7 +5152,7 @@ set_limits('INST', 'HEALTH_STATUS', 'TEMP1', -10.0, 0.0, 50.0, 60.0, 30.0, 40.0,
 
 ### set_state_color
 
-<span class="badge badge--secondary since-heading">Since 7.3.0</span>
+<span class="badge badge--secondary since-heading">Since _Coming Soon_</span>
 
 The set_state_color method changes the color associated with a telemetry item's state in realtime. Items with states (e.g. CONNECTED, UNAVAILABLE) use a state color (GREEN, YELLOW, or RED) to determine their limits state rather than numeric red/yellow/green limits. Note: In most cases it would be better to update your config files rather than changing state colors in realtime.
 

openc3/data/config/target.yaml

@@ -179,7 +179,7 @@ TARGET:
         LOG evaluates limits and logs state changes but does not trigger limits reactions
         or update the current limits state used by the API.
         DISABLE skips limits processing entirely for stored packets.
-      since: 7.3.0
+      since: _Coming Soon_
       parameters:
         - name: Mode
           required: true

scripts/release/openc3_set_versions.rb

@@ -238,3 +238,30 @@
   end
   puts "Updated: #{full_path}"
 end
+
+# Replace "_Coming Soon_" markers with the actual release version. These mark
+# features that ship in this release (e.g. 'since: _Coming Soon_' in config
+# YAML and 'Since _Coming Soon_' badges in the docs). Only do this on a
+# production release so the "next version" (prerelease) update doesn't consume
+# the markers before the feature has actually shipped.
+if is_prod_release
+  coming_soon_globs = [
+    File.join(base_path, 'openc3', 'data', 'config', '*.yaml'),
+    File.join(base_path, 'docs.openc3.com', '**', '*.md'),
+    File.join(base_path, 'docs.openc3.com', '**', '*.mdx'),
+  ]
+
+  Dir.glob(coming_soon_globs).uniq.sort.each do |full_path|
+    data = nil
+    File.open(full_path, 'rb') do |file|
+      data = file.read
+    end
+    next unless data.include?('_Coming Soon_')
+
+    data = data.gsub('_Coming Soon_', version)
+    File.open(full_path, 'wb') do |file|
+      file.write(data)
+    end
+    puts "Updated: #{full_path}"
+  end
+end