chore(release): v0.4.6 - #53
Conversation
|
ClawSweeper status: review started. I am starting a fresh review of this pull request: chore(release): v0.4.6 This is item 1/1 in the current shard. Shard 0/1. This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking. Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted. |
|
Release-owner decision: cut After this PR is squash-merged, create the protected annotated The exact release head has green CI and native Windows proof for trusted-owner |
What Problem This Solves
The Windows ownership hardening merged after
v0.4.5, but the npm package andGitHub release still expose
0.4.5.Why This Change Was Made
Bump the package to
0.4.6and date the existing release notes so the protectedtag workflow can publish the already-merged security fix. This PR changes release
metadata only.
User Impact
Consumers can install a release that rejects foreign-owned or unverifiable
Windows files during secure reads while preserving trusted local owners and
exact extended drive paths.
Evidence
pnpm check: 43 files passed; 461 tests passed, 4 skipped; build, lint,tarball, and import checks passed.
pnpm test:security: 5 files and 59 tests passed.Native Windows release proof on Node
24.15.0and pnpm10.34.5:60 focused tests passed, 11 skipped; Administrators-owned normal and exact
\\?\paths were accepted; Builtin Users ownership was rejected withnot-owned.Crabbox run: https://crabbox.openclaw.ai/portal/runs/run_1bd53888f6c7
Autoreview: clean, no accepted or actionable findings.
Tests added or updated when behavior changed
Security and compatibility impact considered
CHANGELOG.mdupdated when release-relevantNo credentials, private paths, private hosts, or sensitive contents included
Related: #48