Skip to content

gentle-pi v3.2.1

Choose a tag to compare

@Alan-TheGentleman Alan-TheGentleman released this 18 Sep 13:32
· 414 commits to main since this release
dce8746

Gentle Shell v3.2.1 pins the matching Gentle AI v3.2.1 runtime, fixes the review inspect committed range, and brands the status bar as gentle shell. The npm package remains gentle-pi.

Provenance

  • Previous stable: v3.2.0 → 2b579c80
  • Release target: v3.2.1 → dce8746852788837fb69545d9fbb5552f07cb307
  • Release validation: run 35350796311 passed package verification and published to npm with provenance.
  • Pinned Gentle AI: v3.2.1 (e7729359); review provider contract 1.2.0 remains unchanged.

What was fixed

Review inspect named the wrong committed range (#1177, #1178)

gentle_review {"operation":"inspect"} with a committed-range selector aligned the inspected range with the requested base, so a candidate no longer inspects bytes outside the range the caller named.

Status bar brand reads "gentle shell" (#1179, #1181)

The status bar brand segment now renders ✿ gentle shell, matching the sidebar banner and the product identity. The compact path segment still shows the working directory's last component; that is the path, not the brand.

docs/review-integration.md byte-pin restored (#1186 follow-up)

#1186 changed the review integration doc without refreshing its byte pin, so main failed the publication gate. The merged bytes are pinned again.

Pinned runtime

The package-local runtime is now Gentle AI v3.2.1, with signed release archives for Darwin and Linux and the SumDB-verified source build for Windows. The provider contract stays at 1.2.0; the native CLI contract row for 3.2.1 repeats 3.1.0 because zero contract bytes changed.

Upgrade

pi install npm:gentle-pi@3.2.1

Restart Pi, then run gentle-ai sync so the managed orchestrator assets match the pinned runtime.

Verification

  • pnpm test green (2726 tests, 2688 pass); contract mirror check and runtime harness passed.
  • Package verification (168 files, 69 byte-pinned contract artifacts), npm pack --dry-run, and the packed-runner E2E against the pinned v3.2.1 release assets.
  • The pin bump went through the native review (high, four lenses) and was approved with one informational follow-up.