Skip to content

v2.0.1 - Re-audit, docs accuracy

Choose a tag to compare

View all tags
@ChaoticSi1ence ChaoticSi1ence released this 29 Aug 11:26
· 4 commits to main since this release
v2.0.1
ef30abc

Documentation accuracy. No behaviour change — slimbrave-linux.py and slimbrave-mac.py are byte-identical to v2.0.0, and the only code change is one tooltip string in SlimBrave.ps1.

Re-audit: everything still lines up

All 75 policy keys re-verified against chromium/main 3477903 and brave-core master 5f1127a. Zero deprecated, zero renamed, zero with an upper-bounded supported_on — nothing has silently died. Every value SlimBrave writes is still a legal schema member meaning what its label claims, and all three implementations remain in lockstep.

What moved upstream in the two weeks since the last pass, none of it a key this project writes:

  • Chromium went 1,456 → 1,455 policies: a new Relaunch/ group, three reverted ChromeOS local-network-access policies, two additions.
  • RemoteDebuggingAllowed flipped dynamic_refresh false → true — but in M154 territory while Brave stable is on Chromium 152, so its "needs a restart" note is still correct today.
  • Brave stable advanced to 1.94.117 / Chromium 152. Nothing SlimBrave manages was removed or sunset.

Fixed

"Forward-looking" was wrong about Local AI. BraveLocalAIEnabled shipped in v1.9.5 described as forward-looking because Brave 1.94 hadn't released yet. It went stable on 2026-08-27, so the policy is live in the shipping browser — the Windows tooltip and the README both said otherwise. The Brave 1.94+ labels are unchanged and still accurate.

AUDIT.md now keeps a re-audit log

Each pass records the exact upstream revisions it read, so the next one diffs against them instead of re-verifying 75 keys from scratch. Superseded rows keep their original wording and are marked stale inline rather than being rewritten, because the reasoning is the audit trail.

That caught something worth writing down: PsstEnabled's rationale is half-lapsed. It was excluded as "a no-op twice over" — feature-flag-disabled and on no release branch. The YAML now ships on 1.95.x, so the re-check trigger is the kEnablePsst flag rather than a branch appearing. Still correctly unexposed.

Verifying this release

bd23a463f6ebe1f1ddfc99074d474570aa411645e1c639d9422ad059ac5fa0ee  SlimBrave.ps1
29bf69edbe2fb5cea22dd1be4900ab643bc08d0f70a1a5366caa57471e0219bc  slimbrave-linux.py
1d01de4d1bfba2b8908bb1c0b7dba70418ff6583c6dc505c963454d2b2d211a0  slimbrave-mac.py

The two Python sums are unchanged from v2.0.0 — if you are on Linux or macOS there is nothing to update.

Get-FileHash -Algorithm SHA256 .\SlimBrave.ps1

Tags are not signed — there's no maintainer signing key published yet, so don't read an unsigned tag as a sign of tampering. See SECURITY.md.

Assets 3
Loading