chore(release): v3.4.1 — maintenance & data hygiene#410
Merged
Conversation
Stamp the release version across the three pinned locations (CI enforces schemaVersion == ModuleVersion, validate.yml:131): - CheckID.psd1 ModuleVersion 3.4.0 -> 3.4.1 - data/registry.json schemaVersion 3.4.0 -> 3.4.1; dataVersion -> 2026-06-13 - scripts/Build-Registry.py SCHEMA_VERSION 3.4.0 -> 3.4.1 CHANGELOG: stamp [Unreleased] -> [3.4.1] - 2026-06-13 with a theme line and open a fresh [Unreleased]. Patch per VERSIONING.md — all bundled items are data-only corrections (SSPR-002 false-claim flip, SSPR-003 coverage restore, collector rename, #347 enrichment materialization, ADR docs); no schema, registry-field, or module-API shape change. Also re-applies the non-breaking framing correction to the collector-rename entry: the #408 squash-merge landed the pre-correction "breaking" wording on main; M365-Assess PR #982 (merged) dual-names the collector, so the rename is non-breaking. registry.json is version-stamped in place, not rebuilt — the upstream scf.db isn't available locally and the [Unreleased] data was already materialized by its own PRs; a rebuild would only risk unrelated SCF drift.
Content enrichment populationOverall (1106 checks): rationale 26.4% (292/1106) • impact 26.4% (292/1106) • references 26.4% (292/1106)
Informational only — does not gate the build. The hard release-gate for Critical/High enrichment lives in #281 (v3.2.0). |
Framework mapping count delta
Result: ✓ PASS — no framework mapping regressions detected. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Release-prep PR for v3.4.1 — a patch release bundling the current
[Unreleased]changes. Stamps the version and opens a fresh[Unreleased].Per VERSIONING.md, every bundled item is data-only (corrections + a restored manual check + enrichment materialization + ADR docs) — no schema, registry-field, or module-API shape change, so this is a patch, not a minor. (v3.5.0 stays reserved for milestone #44's schema-level work.)
Version stamp (CI-pinned:
schemaVersion==ModuleVersion)CheckID.psd1ModuleVersiondata/registry.jsonschemaVersion(+dataVersion→2026-06-13)scripts/Build-Registry.pySCHEMA_VERSIONCHANGELOG.md[Unreleased]→[3.4.1] - 2026-06-13+ theme, fresh[Unreleased]registry.jsonis version-stamped in place, not rebuilt — the upstreamscf.dbisn't available locally and the[Unreleased]data was already materialized by its own PRs; a rebuild would only risk unrelated SCF drift.What's in this release
ENTRA-SSPR-002false-automation claim corrected; CIS M365 v6 §5.2.4.1 coverage restored asENTRA-SSPR-003StrykerReadiness→CriticalExposure(M365-Assess #968); feat: capture full CIS M365 v6 dataset per check (27 columns) #347 CIS M365 v6 phase-1 enrichment materializedAlso corrects a stale CHANGELOG entry
The #408 squash-merge landed the pre-correction "breaking" wording for the collector-rename entry on
main(my follow-up correction commit didn't make the squash). This PR restores the accurate non-breaking framing — M365-Assess PR #982 (merged) dual-names the collector, so the rename propagates with no flag-day.Verification
registry-integrity.Tests.ps1: 44 passed / 0 failed — incl. "schemaVersion is pinned to CheckID.psd1 ModuleVersion", "schemaVersion is valid semver", "Has dataVersion field with valid date format", "Collector values are from the known set"python -m py_compile scripts/Build-Registry.py3.4.1;dataVersion2026-06-13After merge (separate, with your approval)
Tag
v3.4.1onmain+ push → firesnotify-downstream.yml(checkid-releaseddispatch) → M365-Assesssync-checkidflips the collector value. Then draft the GitHub release from this CHANGELOG section.