From a585c57cda45914a1c4ea7ddabcbfe23df901048 Mon Sep 17 00:00:00 2001 From: Sofeso Date: Sat, 18 Jul 2026 20:10:29 +0100 Subject: [PATCH] Fix stale v4.0.3-4.3.3 <-> v5.0.0-13.2.4 mapping The v4.0.3<->v5.0.0 mapping files claimed v4.0.3-4.3.3 (step-up auth / approval for changing credential or connection-parameter config) was 'MOVED TO'/'MOVED FROM' v5.0.0-13.2.4. That's no longer true: 13.2.4's current text ('Verify that an allowlist is used to define the external resources or systems with which the application is permitted to communicate...') is unrelated to 4.3.3's topic. Verified independently: - 4.0/en/0x20-V12-Files-Resources.md V12.6.1 text matches current v5.0.0 13.2.5 almost word-for-word (server-layer allowlist), consistent with 13.2.5's own mapping tag 'MOVED FROM v4.0.3-12.6.1'. - No V4.0.3 requirement anywhere matches 13.2.4's actual text (app-layer allowlist for outbound communication) - it has no v4.0.3 lineage at all. - The intermediate bleeding-edge mapping files (mapping_v4.0.3_to_v5.0.be.yml, mapping_v5.0.be_to_v4.0.3.yml) correctly show v4.0.3-4.3.3 -> v5.0.be-14.7.3, and mapping_v5.0.be_to_v5.0.0.yml correctly renumbers v5.0.be-14.7.3 -> v5.0.0-13.2.4. That renumbering was accurate at the time; it's the later v5.0.0 restructuring where 13.2.4's *content* (not just its ID) was overwritten by unrelated 12.6.1-derived text that same day 13.2.5 was created, per the commit history laid out in #3344. So only the final v4.0.3<->v5.0.0 mapping files are stale - the 'be' intermediate files still accurately describe that stage. Changed: - v4.0.3-4.3.3: MOVED TO v5.0.0-13.2.4 -> DELETED - v5.0.0-13.2.4: MODIFIED, MOVED FROM v4.0.3-4.3.3 -> ADDED This only corrects the mapping bookkeeping to match what the standard's text actually says today. It intentionally does NOT touch any requirement text, and does not decide the separate policy question #3344 raises (whether the lost 4.3.3-derived control should be restored) - that's for maintainers to decide, so this does not close #3344 on its own. Related to #3344 --- 5.0/mappings/mapping_v4.0.3_to_v5.0.0.yml | 2 +- 5.0/mappings/mapping_v5.0.0_to_v4.0.3.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/5.0/mappings/mapping_v4.0.3_to_v5.0.0.yml b/5.0/mappings/mapping_v4.0.3_to_v5.0.0.yml index 09b7365163..cda27410aa 100644 --- a/5.0/mappings/mapping_v4.0.3_to_v5.0.0.yml +++ b/5.0/mappings/mapping_v4.0.3_to_v5.0.0.yml @@ -248,7 +248,7 @@ v4.0.3-4.3.1: v4.0.3-4.3.2: tag-v5.0.0: SPLIT TO v5.0.0-13.4.1, v5.0.0-13.4.3 v4.0.3-4.3.3: - tag-v5.0.0: MOVED TO v5.0.0-13.2.4 + tag-v5.0.0: DELETED v4.0.3-5.1.1: tag-v5.0.0: MOVED TO v5.0.0-15.3.7 v4.0.3-5.1.2: diff --git a/5.0/mappings/mapping_v5.0.0_to_v4.0.3.yml b/5.0/mappings/mapping_v5.0.0_to_v4.0.3.yml index faaf261dc7..7237a1c235 100644 --- a/5.0/mappings/mapping_v5.0.0_to_v4.0.3.yml +++ b/5.0/mappings/mapping_v5.0.0_to_v4.0.3.yml @@ -511,7 +511,7 @@ v5.0.0-13.2.1: v5.0.0-13.2.3: tag-v4.0.3: GRAMMAR, MOVED FROM v4.0.3-2.10.2 v5.0.0-13.2.4: - tag-v4.0.3: MODIFIED, MOVED FROM v4.0.3-4.3.3 + tag-v4.0.3: ADDED v5.0.0-13.2.5: tag-v4.0.3: GRAMMAR, MOVED FROM v4.0.3-12.6.1 v5.0.0-13.2.2: