Skip to content

Releases

SpecPlanner 0.5.1

Choose a tag to compare

@fiddeb fiddeb released this 15 Nov 19:14

SpecPlanner 0.5.1 provides a release package for planning and reviewing software with Codex, OpenSpec and Excalidraw.

Download specplanner-0.5.1.tar.gz and SHA256SUMS below. GitHub's automatic source archives do not contain the compiled plugin. Verify the checksum, extract the tarball, and follow the included README. The package needs Node 22.13+ in the 22.x line or Node 24+; no npm install is needed inside it.

Changes:

  • Patch five transitive dependencies; npm audit reports zero known vulnerabilities for the tested lockfile.
  • Validate persisted panel connections and make waiting/connected states explicit.
  • Strengthen TypeScript checks and reuse existing behavior verification.
  • Ship a self-contained Codex marketplace, source-commit provenance and SHA-256 checksums.
  • Consolidate documentation and add a panel guide and security-reporting policy.

Verification:

  • All 68 source tests, type checking, build and isolated package verification passed on Ubuntu with Node 22.13.0, 24 and 26.
  • Actual Orca 1.4.259 on macOS passed project binding, official OpenSpec creation/validation, document/comment persistence, stale-write rejection and worker restart checks. Standard installation from the extracted archive connected and rendered successfully.
  • The extracted package installed in Codex CLI 0.164.0. Its cache passed isolated MCP/package checks; a fresh app-server discovered the skill and all 23 MCP tools without a model invocation.
  • The release's server and worker hashes match the actual-host-tested binaries. build-info.json records the exact source commit.

Native-host verification covers local macOS repositories in Orca. Codex desktop conversation-panel placement and light-theme rendering remain unverified; remote Orca repositories are unsupported. A clean dependency audit is not a comprehensive application security audit.

Report defects in GitHub Issues and suspected vulnerabilities through private vulnerability reporting. Detailed evidence and limits are in docs/validation-0.5.1.md inside the package and source repository.