Skip to content

chore(release): v0.4.6 - #53

Merged
vincentkoc merged 1 commit into
mainfrom
release/v0.4.6
Jul 24, 2026
Merged

chore(release): v0.4.6#53
vincentkoc merged 1 commit into
mainfrom
release/v0.4.6

Conversation

@vincentkoc

Copy link
Copy Markdown
Member

What Problem This Solves

The Windows ownership hardening merged after v0.4.5, but the npm package and
GitHub release still expose 0.4.5.

Why This Change Was Made

Bump the package to 0.4.6 and date the existing release notes so the protected
tag 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.0 and pnpm 10.34.5:
    60 focused tests passed, 11 skipped; Administrators-owned normal and exact
    \\?\ paths were accepted; Builtin Users ownership was rejected with
    not-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.md updated when release-relevant

  • No credentials, private paths, private hosts, or sensitive contents included

Related: #48

@vincentkoc vincentkoc self-assigned this Jul 24, 2026
@vincentkoc
vincentkoc marked this pull request as ready for review July 24, 2026 10:28
@vincentkoc
vincentkoc requested a review from a team as a code owner July 24, 2026 10:28
@clawsweeper

clawsweeper Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

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.

@vincentkoc

Copy link
Copy Markdown
Member Author

Release-owner decision: cut v0.4.6 now.

After this PR is squash-merged, create the protected annotated v0.4.6 tag on
the resulting main merge commit. The tag-driven workflow is the only publish
path; no local npm publish will be used.

The exact release head has green CI and native Windows proof for trusted-owner
normal and extended paths plus foreign-owner rejection.

@vincentkoc
vincentkoc merged commit 9b52f71 into main Jul 24, 2026
15 checks passed
@vincentkoc
vincentkoc deleted the release/v0.4.6 branch July 24, 2026 10:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant