From 867409adedb8a9dce424f0605e29a16f77876368 Mon Sep 17 00:00:00 2001
From: HarrietAlexander <153020000+HarrietAlexander@users.noreply.github.com>
Date: Thu, 27 Nov 2025 14:38:15 +1300
Subject: [PATCH] Update config-as-code-runbooks.md

removal of availability call out
---
 src/pages/docs/runbooks/config-as-code-runbooks.md | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/src/pages/docs/runbooks/config-as-code-runbooks.md b/src/pages/docs/runbooks/config-as-code-runbooks.md
index 9772d6ee6c..3ce2d2910a 100644
--- a/src/pages/docs/runbooks/config-as-code-runbooks.md
+++ b/src/pages/docs/runbooks/config-as-code-runbooks.md
@@ -1,16 +1,13 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2024-11-24
-modDate: 2025-02-18
+modDate: 2025-11-27
 title: Config as Code runbooks
 description: Details about using configuration as code with runbooks.
 navOrder: 20
 icon: fa-brands fa-git-alt
 ---
 
-:::div{.success}
-Support for CaC Runbooks is rolling out to Octopus Cloud as of Q1 2025 and will be available in Octopus Server in a future release.
-:::
 
 Config as Code (or CaC) Runbooks stores your runbook process as code in your project repository. This means that you can now use version control to track changes to your runbook processes alongside changes to your project code.