Skip to content

v0.8.1

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 14 Sep 01:46
· 5 commits to main since this release
v0.8.1
This tag was signed with the committer’s verified signature.
steipete Peter Steinberger
SSH Key Fingerprint: 0R9sOfREAbuojItYW9O6fvh2RHbgqVJyvk8FBS/35dk
Verified
Learn about vigilant mode.
aa0565d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Highlights: Nested-project repairs stop tripping over sibling changes, and failed patch attempts keep the edits a provider already wrote.

  • Fixed nested-project repairs to ignore their own state and sibling changes, fingerprint project-relative source paths, and record both sides of renames.
  • Preserved observed source edits in failed patch attempts when a provider writes files before exiting with an error.
  • Fixed doctor to honor standalone provider configuration before project initialization.
  • Prevented oversized provider, validation, and PR-publishing timeout overrides from overflowing into one-millisecond deadlines.
  • Rejected inherited object-property names as unsupported providers instead of failing during harness invocation.
  • Completed Vitest 5 tooling with matching V8 coverage, a full-suite CI coverage run, ignored report artifacts, and documented development Node requirements while retaining Node 22/24/26 CI and the CLI's Node 22 floor.
  • Updated Nano ID to 3.3.19, Magic String to 1.3.1, and Obug to 2.2.1 within the 48-hour dependency release-age policy.
  • Updated Zod and development tooling, aligned Node typings with the Node 22 floor, and added Node 22/24 runtime CI with pinned GitHub Actions.
  • Updated workflow and architecture docs to match current providers, explicit PR creation, validation order, and stale-lock recovery.

Package

Verification

  • Release commit: aa0565d82cafd2de88678be8baff338d26d9664d, landed in #216.
  • CI, CodeQL, and secret scanning passed on the exact release commit. CI covered Node 22, 24, and 26, Windows execution tests, full-suite V8 coverage, build, and packaged CLI smoke.
  • Trusted publishing workflow passed release validation on Node 24, published npm with provenance through the npm-release environment, and created this release.
  • Local validation with Node 24.21.0 and pnpm 11.26.0 passed frozen install, typecheck, lint, formatting, 957 tests (two platform skips), build, package-content checks, and website smoke. Coverage reported 89.45% lines; package smoke mapped 13 features, including three CUDA features. Independent review found no actionable P0–P2 findings.
  • A Node 24 PR CI run exposed a transient ENOTEMPTY race during temporary Git fixture cleanup. Three bounded filesystem retries fixed the test cleanup; the complete local gate and all CI checks passed afterward.
  • Downloaded the published npm tarball (371274 bytes) and verified SHA-512 integrity and SHA-1 against the registry. npm reports latest: 0.8.1, and its gitHead matches the release commit. Previous npm latest was 0.8.0.
  • Installed the downloaded published package into a fresh directory. The installed CLI returned 0.8.1; init, map, status, and report passed against a synthetic Node project, mapping four features with zero findings and zero active locks.
Assets 2
Loading