From 825e217a7982ae30634d921df0b7e4442cd39860 Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Wed, 24 Jun 2026 14:49:34 +0000
Subject: [PATCH 1/2] docs: remove deprecated Approvals section from Getting
 Started

---
 config/navigation.json           |  3 +--
 getting_started/approvals.md     | 11 -----------
 labs/lab-05-runtime-controls.mdx |  1 -
 3 files changed, 1 insertion(+), 14 deletions(-)
 delete mode 100644 getting_started/approvals.md

diff --git a/config/navigation.json b/config/navigation.json
index 4c53f95..37ee336 100644
--- a/config/navigation.json
+++ b/config/navigation.json
@@ -27,8 +27,7 @@
             "getting_started/attestations",
             "getting_started/environments",
             "getting_started/policies",
-            "getting_started/enforce_policies",
-            "getting_started/approvals"
+            "getting_started/enforce_policies"
           ]
         },
         {
diff --git a/getting_started/approvals.md b/getting_started/approvals.md
deleted file mode 100644
index 2738dd9..0000000
--- a/getting_started/approvals.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Approvals"
-description: "Learn about approvals in Kosli"
-icon: "check-double"
----
-
-When an artifact is ready to be deployed to a given [environment](/getting_started/environments/), an approval may be reported to Kosli. An approval can be requested which will require a manual action, or reported automatically. This will be recorded in Kosli so the decision made outside your CI system won't be lost.
-
-When an approval is created for an artifact to a specific environment with the `--environment` flag, Kosli will generate a list of commits to be approved. By default, this list will contain all commits between `HEAD` and the commit of the most recent artifact coming from the same [flow](/getting_started/flows/) found in the given environment. The list can also be specified by providing values for `--newest-commit` and `--oldest-commit`. If you are providing these commits yourself, keep in mind that `--oldest-commit` has to be an ancestor of `--newest-commit`.
-
-See [request approval](/client_reference/kosli_request_approval/) and [report approval](/client_reference/kosli_report_approval/) for usage details and examples.
diff --git a/labs/lab-05-runtime-controls.mdx b/labs/lab-05-runtime-controls.mdx
index c6fb6a7..4c1ddef 100644
--- a/labs/lab-05-runtime-controls.mdx
+++ b/labs/lab-05-runtime-controls.mdx
@@ -233,7 +233,6 @@ You have full visibility and control over your software supply chain, from build
 
 - [Custom attestation types](/getting_started/attestations) for your specific tools
 - [Kubernetes environment reporting](/tutorials/report_k8s_envs) if you use K8s
-- [Approvals](/getting_started/approvals) for production deployment workflows
 
 **Further reading:**
 - [Environments](/getting_started/environments)

From fdd15f76c3ec27cb66aa886b8dcca9e3d3a4bb53 Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Wed, 24 Jun 2026 14:59:07 +0000
Subject: [PATCH 2/2] docs: redirect /getting_started/approvals to attestations

---
 config/redirects.json | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/config/redirects.json b/config/redirects.json
index 84e3956..20c660c 100644
--- a/config/redirects.json
+++ b/config/redirects.json
@@ -1,4 +1,8 @@
 [
+  {
+    "source": "/getting_started/approvals",
+    "destination": "/getting_started/attestations"
+  },
   {
     "source": "/ci-defaults",
     "destination": "/integrations/ci_cd"