mirror of https://github.com/raandree/NTFSSecurity
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1.8 KiB
1.8 KiB
| status | last-verified | owner | source |
|---|---|---|---|
| current | 2026-10-04 | active-agent | current task evidence |
Active context
Current focus
5.0.0-rc1 is published (Gallery and GitHub prerelease, #98, tag
5.0.0-rc1) and verified. The maintainer tests it; after that comes the
final 5.0.0 release (remove the label, date the changelog, tag 5.0.0),
then work package 5 (code defects) and the open issues. The local branch
ai/memory-bank-rc1 holds this note and rides along with the next PR.
Evidence
- Release run 37230802387: build, tests in both editions, packages, release checks, Gallery publish, and GitHub release all passed; the wiki job skipped the tag as designed.
- The Gallery nupkg (275,437 bytes) is byte-identical to the CI artifact,
and the GitHub
NTFSSecurity.zipto the CI zip; all 11 module files match. The DLLs are optimized Release builds (JIT optimizer enabled). - Gallery:
IsPrereleasetrue,IsAbsoluteLatestVersiontrue,IsLatestVersionfalse; stableFind-PSResourcereturns 4.2.6, with-Prerelease5.0.0-rc1. 85 tags with all 36PSCmdlet_and 36PSCommand_; the Gallery itself addsPSEdition_CoreandPSEdition_Desktop. - Installed with
Save-PSResourceand copied tobin\Release, the module passes the full suite: Windows PowerShell 261 passed, 7 skipped; PowerShell 7 232 passed, 36 skipped. - The command search (
Find-PSResource -CommandName) still returned 4.2.6 at 20:16 UTC, four minutes after publishing; the search index was stale, because it treated 4.2.6 as the absolute latest version. - The wiki was republished from
e0f5366; Home mentions-AllowPrerelease.
Next step
Recheck the command search for 5.0.0-rc1. When the maintainer reports test
results: prepare the final 5.0.0 release PR, or fix what the tests found
and publish 5.0.0-rc2.