From 408ebc493cdbd6e309b02ff9d1057e822b45be82 Mon Sep 17 00:00:00 2001
From: Matthew Jackson <1085847+MattJackson@users.noreply.github.com>
Date: Mon, 29 Jun 2026 01:21:46 -0700
Subject: [PATCH] =?UTF-8?q?docs:=201.2.0=20changelog=20=E2=80=94=20drop=20?=
 =?UTF-8?q?pre-1.1.0=20carryover=20entries?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The 'KeydbSource owns save+update' (Added) and 'Processing-Key
decryption restored' (Fixed) entries were stale carryover from the
never-released 1.1.0-beta.1; that code shipped in v1.1.0 (zero diff in
v1.1.0..HEAD). The 1.2.0 entry now lists only the real 1.2.0 changes
(hex unification, DiscInputs version stride, MKB cap).
---
 CHANGELOG.md | 14 --------------
 1 file changed, 14 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index aabd4d2..7fff39c 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,11 +2,6 @@
 
 ## [1.2.0] — 2026-06-28
 
-### Added
-
-- `KeydbSource` now owns keydb save + update (atomic write to the source's own
-  path); honors the caller-supplied location.
-
 ### Changed
 
 - **One hex parser across the toolchain.** Online and keydb hex inputs now parse
@@ -18,12 +13,3 @@
   at their own stride.
 - **Online MKB read cap aligned with libfreemkv (64 MiB)**, and an over-cap MKB
   is logged rather than silently truncated.
-
-### Fixed
-
-- **Processing-Key decryption restored.** A keydb Processing Key is again driven
-  through the full AACS chain — PK → Media Key (against this disc's own MKB) →
-  Volume Unique Key (with the disc Volume ID) → unit keys — so discs that ship
-  only a Processing Key decrypt again. Stored Media Keys and Volume Unique Keys
-  are still honored directly. (Cross-disc Media-Key reuse remains intentionally
-  disabled.)