Changelog

Every release, dated and tagged.

Regulated buyers read changelogs to judge whether a vendor is disciplined. Breaking changes are flagged, deprecations carry a stated window, and security fixes are published even when they are dull.

Current release
v1.2.4
Cadence
Fortnightly, Thursdays SGT
Deprecation window
Two minor versions, min 90 days
Breaking changes, last 12 mo
2
In-flight runs
Continue on their own release

All Studio Hub Runtime Governance Packs Security API & CLI

v1.2.4 · 14 August 2026

Stableno breaking changes
  • Runtime New Credit reservation and per-checkpoint settlement

    Runs now reserve the crew's recent P90 run cost plus a variance buffer at admission and settle at each checkpoint. A run that exhausts the wallet parks in awaiting_credit for 72 hours and auto-resumes on top-up rather than failing. Side-effect Actions are withheld while a wallet is short.

  • Governance New Reviewer calibration metrics

    Sampling regimes now report reviewer agreement, median decision time and override rate per reviewer. Autonomy graduation is blocked when reviewer agreement falls below the configured bound.

  • Studio Improved Diff-before-apply for plain-English changes

    Change plans now show the manifest diff, the validation result and the sample test run on one screen, with per-hunk accept. Previously accept was all-or-nothing.

  • Packs Improved Singapore Legal Practice Pack v4.1

    Clause library refreshed to 31 July 2026 currency. Twelve new evaluation cases drawn from disputed tenancy matters. Change notice sent to entitled tenants.

  • API & CLI Fixed krewos run audit pagination

    Exports over 10,000 trace records truncated silently at the page boundary. Records were never lost, but the export was incomplete. Affected exports can be regenerated.

  • Security Fixed Secret reference redaction in support tooling

    A support view could render the last four characters of a tenant-managed secret reference identifier. No key material was ever exposed. Reported through the disclosure programme, fixed within 48 hours.

v1.2.3 · 31 July 2026

Breakingmigration required

Breaking change. Effect Declarations now require an explicit compensation block on every Action. Manifests without one fail validation. Announced 5 May 2026, 87 days of notice. Run krewos manifest migrate --to 1.2.3 to add scaffolded declarations for review.

  • Governance Breaking Mandatory compensation behaviour on Actions

    Every declared external effect must state what happens if it needs to be undone. Undoable actions declare compensation: none explicitly, which is a decision rather than an omission.

  • Runtime New Canary releases

    Route a configurable share of production traffic to a candidate release with automatic reversion on evaluation-gate breach. Professional and above.

  • Hub Improved Private tenant catalogues

    Publish verified components to your own organisation without publishing to the world. Lineage and verification tier are tracked identically.

  • Runtime Deprecated runs.list v1 endpoint

    Superseded by runs.search with cursor pagination. Removal no earlier than v1.4.0 or 30 November 2026, whichever is later.

v1.2.2 · 17 July 2026

Stable
  • Governance New Staleness propagation

    When a source expires or materially changes, every artefact that relied on it is identified and its owners notified, with the affected claims listed. Previously staleness was visible only on the Knowledge Pack itself.

  • Governance New Conflict carry-forward

    Where sources of comparable authority disagree, both positions are carried into the evidence record and surfaced to the reviewer. The system no longer silently prefers the higher-ranked retrieval.

  • Packs New Aquaculture Operations Pack v2.0

    Adds barramundi and grouper knowledge packs, revised dissolved-oxygen safety rules, and 40 evaluation cases built from real incident reports.

  • API & CLI Improved krewos validate taint analysis output

    Failures now print the full path from untrusted input to the ungated effect, rather than naming only the offending node.

v1.2.1 · 3 July 2026

Stablesecurity
  • Security Fixed Dependency advisories in the sandbox image

    Three moderate advisories in the code-execution sandbox base image. No exploitation observed. Patched image rolled to all regions within the maintenance window.

  • Runtime Fixed Duplicate task notification on escalation

    Escalating an approval task could notify the original assignee twice. The Correction Record and the audit trail were always correct; only the notification duplicated.

  • Studio Improved Cost estimate on the canvas

    Per-node credit estimates now split platform and model meters, and respect a BYOK configuration when one is attached.

v1.2.0 · 19 June 2026

Major
  • Governance New Progressive autonomy, generally available

    Four-stage graduation with risk-weighted sampling, published confidence bounds and automatic reversion on breach. Regulated crews can be pinned to the permanent full-review floor.

  • Runtime New Compile-time proof of gated effects

    The validator now proves statically that no path runs from untrusted input to an external side effect without an intervening approval gate. If the property does not hold, no release is produced.

  • Hub New Verification tiers

    Draft, Tested, wGrow verified, Tenant verified and Deprecated, each with published criteria. Compatible updates may be recommended but are never installed silently.

  • API & CLI New MCP server and client

    Deployed crews are callable as MCP tools with policy and approval enforced by the runtime. Approved external MCP servers are consumable as Tools, with per-tool admission control.

How we version

Breaking changes

Announced at least 90 days ahead, flagged in the changelog and by email to workspace administrators, with a migration command where one is possible.

Deprecations

Supported for at least two minor versions or 90 days, whichever is longer. Removal dates are published when the deprecation is announced, not later.

In-flight runs

A long-running case continues on the release it started on, even after you deploy or roll back. Releases are immutable and dependency-locked, so nothing changes underneath a matter that is already open.

wGrow Technologies Pte Ltd · Singapore · Release notes cover the Control Plane, Execution Plane, Studio, Hub and first-party Packs. Pack publishers maintain their own change notices for entitled tenants.