Skip to content

Release v1.5.0

Choose a tag to compare

@damienSavoldelli damienSavoldelli released this 15 Mar 12:36
· 77 commits to main since this release
8f6b8e7

What changed

  • Added provider capability contracts in the registry using tri-state support:
  • supported
  • unsupported
  • unknown
  • Added execution safety/diagnostic CLI flags:
  • --strict-capabilities
  • --dry-run
  • --print-effective-config
  • Added capability validation before execution:
  • default permissive mode: warning + continue
  • strict mode: fail-fast on unsupported/unknown requested capabilities
  • Added dry-run preflight behavior:
  • validates resolved provider/runtime config
  • validates capability compatibility
  • exits without provider generation and without writing artifacts
  • Added effective-config diagnostics with masked API key handling.
  • Updated documentation (README + technical docs) to reflect v1.5 safety and preflight behavior.

Why it matters

  • Reduces runtime surprises by checking feature compatibility before execution.
  • Improves operational safety for CI/automation workflows.
  • Adds reproducible preflight diagnostics for debugging configuration issues.
  • Preserves the existing stateless execution architecture while improving reliability.

Stability Statement

  • v1.5.0 is a stable feature release.
  • No CLI breaking changes were introduced.
  • No output JSON schema/contract breaking changes were introduced.
  • Stateless single-execution design remains unchanged.

Scope Clarification

  • This release does not introduce agents, memory, orchestration, tool-calling runtime, or multi-
    turn workflows.
  • The tools capability is currently a reserved contract field for future compatibility checks and
    remains unsupported at runtime.

GitHub Pull Requests Included

Full Changelog: v1.4.0...v1.5.0