Skip to content

PRAXO-CORE 2.5.1

Released: 2026-10-28

PRAXO-CORE 2.5.1 is a patch release for security and behavior corrections after 2.5.0. Exported pkg/... declarations are unchanged; the API snapshot differs only in package comment text.

Highlights

  • PII history redaction. The PII middleware now redacts historical tool-call arguments before they return to a model, including nested values, and handles typed map[string]string / []string tool results. Live invocation arguments remain available to policy and approval code.
  • Execution cleanup. Failed startup paths run cleanup for middleware that was already entered, remaining AfterRun callbacks run after an error, and call-limit/tool-selection state is released even when a failed run has no result. Original execution errors remain primary.
  • Cancellation and parallelism. Tool execution no longer starts another tool after cancellation, including tools waiting for a parallel slot.
  • Context compaction. Compaction output is applied even when replacing an older message with a marker leaves the message count unchanged.
  • OpenAI-compatible adapter. Truncated streams without [DONE] or a finish reason are rejected, cached prompt tokens are mapped, and existing multimodal blocks / schema response formats are honored instead of silently dropped.
  • Scheduler, formatter, and process containment. Invalid schedules are rejected, formatter per-file failures are reported, and Windows Job Object handle operations are serialized.
  • Conformance gates. Go, C, and language runners reject missing or empty required vector groups in the cases listed in CHANGELOG.md.

Upgrade

go get github.com/axisvela/praxo-core/v2@v2.5.1

No source migration is required from 2.5.0. This release does not change the plugin manifest, event names, stream kinds, or other wire contracts.

Language Core implementations and adapters are versioned independently. Their PII/runner changes require separate language or adapter tags; this core tag does not publish them.

Validation

  • Root Go tests, vet, build, race, fuzz, staticcheck, and govulncheck are required for the release commit.
  • api/2.5.1.txt adds no exported declarations relative to api/2.5.0.txt.
  • Strict documentation build and same-commit CI/docs checks are required before the release job runs.
  • The release publishes a source archive, SBOM, checksums, and a release manifest.

Limits

  • PII redaction does not cover live tool execution arguments, error strings, event payloads, or arbitrary structs; products own those trust boundaries.
  • Linux process containment remains weaker than a Windows Job Object; cgroup v2 and deterministic WASM fuel remain open.
  • Workspace/session adapters remain offline conformance-tested; live providers and production readiness are not claimed.
  • These checks do not establish independent security review or production deployment.