From 333e6e043ed63257a37e64828cd609acf8e2a689 Mon Sep 17 00:00:00 2001
From: tbartel74 <tomasz@bartel.com.pl>
Date: Tue, 14 Jul 2026 15:11:58 +0200
Subject: [PATCH] docs(sdk): add 2.0 migration guidance to release notes

---
 .github/workflows/release.yml | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 2b01a1e..216c4b5 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -109,6 +109,19 @@ jobs:
             pip install vigil-guard==${{ steps.version.outputs.package_version }}
             ```
 
+            ## Migration from 1.x
+
+            SDK 2.0 accepts anti-recon opaque responses. Check
+            `result.diagnostics_available` before reading diagnostic fields or
+            compare optional diagnostic properties explicitly, such as
+            `result.is_high_risk is True`.
+
+            Before rolling a consumer back to SDK 1.x, disable opaque exposure
+            for that consumer's affected rule sets. A 1.x parser rejects opaque
+            responses, so use a forward fix when that cannot be guaranteed.
+
+            See `CHANGELOG.md` in this release for the complete migration notes.
+
             ## Verification
             SBOM is included in release assets. GPG signatures are included when the release signing key is configured.