Release Notes#

These notes describe the v1.1.1 release relative to v1.1.0. They are based on the tagged implementation changes and the coordinated three-image release set.

Release 1.1.1#

This patch release improves contract-first generation reliability and refreshes runtime dependencies. The application remains a three-container release set with external inference, PostgreSQL, and optional observability.

Highlights#

The release focuses on producing usable contracts and retaining accurate generation evidence.

  • Contract authoring tolerates additional common model-output defects and normalizes supported field and route representations.

  • Structured model output handling is more tolerant of returned formatting.

  • Inference error classification recognizes additional provider status formats while distinguishing transient errors from permanent quota exhaustion.

  • Generation and repair attempts retain validation evidence rather than losing earlier failures when a repair does not succeed.

  • Generated required-field checks target the required fields rather than assuming every field is required.

Dependency Updates#

The release refreshes Python and container dependencies, the GitHub MCP proxy’s dependency pins, and the third-party attribution notice. Check each NGC artifact’s Security Scanning tab for its current scan and VEX results.

Upgrade Compatibility#

The tagged comparison introduces no database schema changes, new environment-template variables, or mandatory secret changes. Update all three application images to 1.1.1, keep the existing database and persistent state, and retain the stable encryption and signing material.

NGC tags use 1.1.1; the source tag is v1.1.1. Registry mirrors can have their own tag conventions. Follow Upgrade from v1.1.0 for the sequence and verification checks.

Known Issues and Operational Boundaries#

The following release boundaries still apply after upgrading.

  • Default auto generation uses the contract-first Cursor path. It does not silently fall back to llm mode.

  • Some comments in the shipped environment template describe older fallback behavior. Use the mode definitions and credential requirements in the Support matrix.

  • An administrator CURSOR_API_KEY requires a declared MODEL_CURSOR; auto selects Cursor’s automatic routing.

  • The Helm production example keeps one backend replica and disables Docker-dependent candidate validation. Review skips before interpreting a generated package as validated for container execution.