Skip to content

v0.4.2

Choose a tag to compare

@Sannrox Sannrox released this 07 Oct 10:04
2a45975

Release notes: v0.4.2

Crate version: 0.4.2. Tag: v0.4.2.

Pair with release readiness. Contributor credits
belong on the GitHub Release generated notes.

Scope

Pre-1.0 patch on published GitHub release
v0.4.1. Operators get
web console
v0.2.0 at
/ui/, which adds environment subscribe, catalog publish, promote, and recall,
and a reconcile tick over the existing tenkai.http.v1 routes. The workspace
is split into crates (#523), which changes source-build feature flags.

Base: tag v0.4.1 (bf0f835). Open release-blocking issues at crate-bump
time: none. Follow-up #511 stays open.

Compatibility and migration

Surface Impact for 0.4.2
Crate version 0.4.1 → 0.4.2 for tenkai and every workspace crate
SQLite SCHEMA_VERSION Remains 12. No migration
Hub Postgres schema Remains 12
Runtime / auth / federated / model / plan / provider contracts Documented *_CONTRACT_VERSION / PLAN_FORMAT_VERSION remain 1
HTTP contract Id stays tenkai.http.v1. Console v0.2.0 requires exactly this contract
Web console ui/console.pin moves from v0.1.0 to v0.2.0
Source builds ui and postgres are tenkai-server features (#523): community --features tenkai-server/ui, hub -p tenkai-server --features postgres,ui
GitHub Release assets Same names as 0.4.1: community ui hosts, hub tenkai-server-postgres-<platform>, tenkai-http-v1.schema.json, SHA256SUMS, and attestations for linux-x86_64 and darwin-aarch64
Toolchain rust-version = "1.96.1"
Defaults Signing/approval fail closed; tenant mode / enterprise flags default off

Operator upgrade notes

  1. Embedded / SQLite: install 0.4.2 hosts from the GitHub Release after
    verifying SHA256SUMS and the attestation. No store migration.
    tenkaictl --version reports tenkaictl 0.4.2. See
    release binaries.
  2. Web console: management actions in the console call the same lifecycle
    routes as tenkaictl and need the management capability. Nothing changes
    in server authorization. A credential refused by the server loses that
    scope's console controls for the session.
  3. Source builds: replace --features ui with --features tenkai-server/ui
    for the workspace, or build -p tenkai-server --features ui. The hub
    build is cargo build --release --locked -p tenkai-server --features postgres,ui.
    TENKAI_UI_BUNDLE still skips the download and still enforces the pinned
    checksum.

Rollback

Previous 0.4.1 binary plus the existing Tenkai-owned SQLite (embedded) or
Postgres (hub) store. No schema change in this patch; the previous binary
serves console v0.1.0 again. Recovery never depends on sekai-chisei.

User-visible changes

Added

  • Web console v0.2.0: subscribe an environment to a product channel; publish,
    promote, and recall releases with signing kept outside the browser; request
    one reconcile tick and read its per-environment report

Changed

  • Workspace split into tenkai-wire, tenkai-http, tenkai-server,
    tenkaictl, tenkai-executor, and tenkai-postgres; ui and postgres
    are now tenkai-server features (#523)

Fixed

  • Web console no longer sends a management action clicked while the browser
    was offline when it reconnects; the outcome shows as unknown instead

Migration

  • None. SCHEMA_VERSION remains 12. HTTP contract id stays tenkai.http.v1.

Out of scope for 0.4.2

  • A route that lists a caller's grants for the console
  • Advertising product high_availability capability
  • Extra platforms or crates.io
  • Rewriting docs/releases/0.4.1.md
  • #511 (export operation-bound feedback observations)