From 5d7dd3804a98f31cedb44fd1c68120fdf33e195d Mon Sep 17 00:00:00 2001 From: Raimund Andree Date: Wed, 21 Oct 2026 07:40:06 +0000 Subject: [PATCH] docs(memory-bank): record the merge of #128 and the CI of #129 and #130 #128 (the rc8 record) merged on 2026-10-21 at 05:48Z, and the tests-only round and this Memory Bank are #129 and #130 with a green CI. On the runner the four configurations give the counts of the local run in each of the 29 test files, so the notes no longer say that the branch is not pushed or that the runner has not run the tests. Records that no plain test gap is left and that the 10 rows that need a decision (7 MaintainerDecision, 3 would-pin) wait for the maintainer. The status paragraph of progress.md drops the list of the merged pull requests of 2026-10-10 that the milestones already carry, which keeps the file within its line budget. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: AI Assistant --- .memory-bank/activeContext.md | 40 ++++++++++--------- .../0021-quality-gate-before-5.0.0.md | 5 ++- .memory-bank/progress.md | 34 ++++++++-------- 3 files changed, 41 insertions(+), 38 deletions(-) diff --git a/.memory-bank/activeContext.md b/.memory-bank/activeContext.md index ae5df9a..68e60ee 100644 --- a/.memory-bank/activeContext.md +++ b/.memory-bank/activeContext.md @@ -9,7 +9,7 @@ source: current task evidence ## Current focus -State at 2026-10-20 14:55 UTC: 5.0.0-rc8 is published and accepted. The +State at 2026-10-21: 5.0.0-rc8 is published and accepted. The maintainer merged #126 (the decisions of 2026-10-19) and #127 (`c719197`: the fix of the false "no access" of `Get-NTFSEffectiveAccess`, the known limit of the hard-link cmdlets in the pages and the CHANGELOG, and the label `rc8`) and @@ -20,15 +20,16 @@ passed. The lab acceptance of the published bytes passed in one detached driver six machine classes, the first lab 245/0/1 per edition, every end state CLEAN (record `Tests/Lab/Acceptance-2026-10-20-published-rc8.md`, #128). The boundary of the new error, a computer name of 32,718 characters, holds on Server 2019, -2022, 2025, and Windows 11 26H1. The tests-only round for the plain gaps ran -the same afternoon (Next step 6; branch `ai/tests-round-1`, not pushed). Open -before the stable pull request: its pull request and the CI on the runner, the -maintainer's #34 decision on 2026-11-02 (no reply to his follow-up of -2026-10-19), and his check of `PSGALLERY_API_KEY`. The stable build is new -bytes that no lab has run; the -procedure accepts the last prerelease, so the stable change touches only the -label, the CHANGELOG, and `$publishedVersions`. Any other product change needs -rc9 and the same acceptance, about 70 minutes with the chain script. +2022, 2025, and Windows 11 26H1. He merged the record, #128, on 2026-10-21 at +05:48Z (`master` `461015e`, CI green). The tests-only round for the plain gaps +ran on 2026-10-20 (Next step 6) and is #129, with this Memory Bank in #130; +their CI is green, and the runner's counts equal the local run in each test +file. Open before the stable pull request: the merge of both, the maintainer's +decision on #34 on 2026-11-02 (no reply to his follow-up of 2026-10-19), and +his check of `PSGALLERY_API_KEY`. The stable build is new bytes that no lab +ran; the procedure accepts the last prerelease, so the stable change touches +only the label, the CHANGELOG, and `$publishedVersions`. Any other product +change needs rc9 and the same acceptance (about 70 minutes with the script). State at 2026-10-10: the maintainer integrated the release-gate stack into `master` (#116, #120, #118, #119, #121; `fa0701b`, CI green; GitHub closed #117 @@ -184,13 +185,14 @@ Decisions 22 and 24 on 2026-10-19 and decides 23 on 2026-11-02. 21): the hard-link names under another root stay a known limit; the pages and the CHANGELOG say so since rc8. The tests-only round for the plain items (68 `budget` mentions) ran on 2026-10-20: four implementers, one - `ParameterSets.*` file each, integrated on `ai/tests-round-1` (`d28c7a0`, not - pushed): 89 `It` blocks, 121 cases, the suite 1,494 to 1,615 per - configuration, 0 failed; 38 of 64 sets closed, 26 with a leftover (16 - Limit, 7 MaintainerDecision, 3 would-pin), no defect; report - `Tests/Coverage/Quality-Gate-Test-Round-2026-10-20.md`. The GitHub runner - has not run the tests yet. A defect that a test finds needs his decision and - rc9. Still his: the silent default scope for a piped `AppliesTo` that - PowerShell cannot convert (a design change), the 8 getters of pipeline - parameters, and the audit paths. + `ParameterSets.*` file each, integrated on `ai/tests-round-1` (#129): 89 `It` + blocks, 121 cases, the suite 1,494 to 1,615 per configuration, 0 failed; + 38 of 64 sets closed, 26 with a leftover (16 Limit, 7 MaintainerDecision, 3 + would-pin), no defect; report + `Tests/Coverage/Quality-Gate-Test-Round-2026-10-20.md`. On the runner (CI run + `39551726767`) the counts equal the local run in each test file. No plain + gap is left. A defect that a test finds needs his decision and rc9. Still + his: the 7 MaintainerDecision and 3 would-pin rows, the silent default scope + for a piped `AppliesTo` that PowerShell cannot convert (a design change), the + 8 getters of pipeline parameters, and the audit paths. 7. Do not release stable 5.0.0 or equate a percentage with gate closure. diff --git a/.memory-bank/decisions/0021-quality-gate-before-5.0.0.md b/.memory-bank/decisions/0021-quality-gate-before-5.0.0.md index 20cfbb4..ce4a81d 100644 --- a/.memory-bank/decisions/0021-quality-gate-before-5.0.0.md +++ b/.memory-bank/decisions/0021-quality-gate-before-5.0.0.md @@ -83,8 +83,9 @@ tests-only round ran the same afternoon (report `Tests/Coverage/Quality-Gate-Test-Round-2026-10-20.md`): 89 `It` blocks, 121 cases, the suite 1,494 to 1,615 per configuration with no failure, 38 of 64 parameter sets closed, 26 with a leftover (16 Limit, 7 MaintainerDecision, 3 -would-pin), no defect. It is on `ai/tests-round-1` and has not run on the -GitHub runner. Open are that pull request, the leftovers until 2026-11-02, #34 +would-pin), no defect. It is #129; on the runner the counts equal the local +run in each test file. No plain gap is left. Open are the merge of #129, the +10 rows that wait for his decision (7 MaintainerDecision, 3 would-pin), #34 (2026-11-02), and the key check. The stable build is new bytes: the stable change may touch only the label, the CHANGELOG, and `$publishedVersions`; any other product change needs diff --git a/.memory-bank/progress.md b/.memory-bank/progress.md index 5a0f0b2..1d10c51 100644 --- a/.memory-bank/progress.md +++ b/.memory-bank/progress.md @@ -11,15 +11,13 @@ source: repository and validation evidence 5.0.0-rc8 is published on the Gallery and GitHub (2026-10-20, tag at `c719197`); rc7 (2026-10-10, tag at `fa0701b`) is the one before it. On -2026-10-10 the maintainer merged the whole stack into `master` (CI green): #116 -(rc7), #120 (it replaced #117, which GitHub closed unmerged when the branch -deletion after #116 removed its base), #118 (the quality-gate paths), #119 (the -operating-system matrix with three module fixes, Decision 24), and #121 (the -Memory Bank). On 2026-10-19 he merged #125 (Handoff 5) and #124 (Dependabot) and -decided the path to stable (Decision 21, "Closing the gate"); on 2026-10-20 he -merged #126 (the decisions) and #127 (the rc8 fix and label) and tagged rc8. -The published rc7 and rc8 passed their lab acceptance in the matrix and in the -first lab. Stable Gallery version: 4.2.6. +2026-10-10 the maintainer merged the stack of #116, #120, #118, #119, and #121 +into `master` (CI green; the milestones have the details). On 2026-10-19 he +merged #125 (Handoff 5) and #124 (Dependabot) and decided the path to stable +(Decision 21, "Closing the gate"); on 2026-10-20 he merged #126 (the decisions) +and #127 (the rc8 fix and label) and tagged rc8; on 2026-10-21 he merged #128 +(the rc8 record). The published rc7 and rc8 passed their lab acceptance in the +matrix and in the first lab. Stable Gallery version: 4.2.6. After 5.0.0, archive in favor of WindowsAccessControl (Decision 18). ## Recent milestones @@ -131,11 +129,13 @@ After 5.0.0, archive in favor of WindowsAccessControl (Decision 18). of 32,718 characters). Record `Tests/Lab/Acceptance-2026-10-20-published-rc8.md` (#128). - 2026-10-20: tests-only round (Decision 21). Four implementers, one - `ParameterSets.*` test file each; integrated on `ai/tests-round-1` - (`d28c7a0`, not pushed): 89 `It` blocks, 121 cases, the suite 1,494 to 1,615 - per configuration, 0 failed in four configurations; 38 of 64 sets closed (7 - before), 26 with a leftover (16 Limit, 7 MaintainerDecision, 3 would-pin); no - defect. Report: `Tests/Coverage/Quality-Gate-Test-Round-2026-10-20.md`. + `ParameterSets.*` test file each; integrated on `ai/tests-round-1` (#129): + 89 `It` blocks, 121 cases, the suite 1,494 to 1,615 per configuration, 0 + failed in four configurations; 38 of 64 sets closed (7 before), 26 with a + leftover (16 Limit, 7 MaintainerDecision, 3 would-pin); no defect. Report: + `Tests/Coverage/Quality-Gate-Test-Round-2026-10-20.md`. On 2026-10-21 the + CI of #129 and #130 passed; the runner's counts equal the local run in each + test file (run `39551726767`). ## Stable capabilities @@ -150,9 +150,9 @@ After 5.0.0, archive in favor of WindowsAccessControl (Decision 18). 1. Decision 21 gate: the published rc7 and rc8 are accepted in the matrix and the first lab (records); stable follows rc8 (Decision 21, "Closing the - gate"). Do not release 5.0.0 until the other gates close: the tests PR (CI - on the runner) and the rest of the plain gaps, #34 on 2026-11-02, and the - key check. Release steps: + gate"). Do not release 5.0.0 until the other gates close: the merge of #129 + and #130 (no plain gap is left), #34 on 2026-11-02, and the key check. + Release steps: `Docs/Contributing/05-Releasing.md`; remove the prerelease label, date `[5.0.0]`, add the last prerelease (rc8) to `$publishedVersions` (never the version of the manifest), tag through CI.