Skip to content

Releases

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 15 Nov 13:04
Immutable release. Only release title and notes can be modified.
v0.4.0
ef364f9

The console for Tenkai 0.9. Same contents as v0.4.0-rc.1.

Upgrade

Tenkai pins the console in ui/console.pin. To serve this release, pin v0.4.0 with the SHA-256 of tenkai-console-v0.4.0.zip from SHA256SUMS. Rollback is pinning the previous zip.

The bundle still requires /healthz to list contract tenkai.http.v1. Types are generated from the signed Tenkai v0.9.0 schema. Against a 0.8 server, the screens for 0.9 routes read as unavailable, a bare-array delivery list reads as the whole list, and a hold by selector reads as refused. Same-origin and air-gapped operation are unchanged.

Added

  • Instance health with checks, observed time, and repairing checks (#155, #172).
  • Channel promotion policy status, soak detail, and pause/resume (#157, #171).
  • What blocks an instance's next change (#159).
  • Automatic environment holds and the failure threshold (#160), and hold by selector with a live match preview (#185).
  • Cancel a running apply, with the cancel outcome, skipped steps, and rollback hold (#162, #174).
  • Sealed secret age and rotation due (#165).
  • Advisory waivers on exposure findings, the waiver list, and grace periods (#166, #180).
  • Environment and release labels, view and edit (#170).
  • Owners and notification endpoints, with owner reachability and single product endpoint removal (#169, #182).
  • Rendered target changes and the approval brief on plans and approvals (#173, #175).
  • Health recall rule: recall details, measured shares, removal progress, and editing the rule (#176, #189).
  • Upgrade pace for a channel from Releases, pacing progress with early admit, and the configured pace next to the pace in effect (#178, #179, #184).
  • Attributed delivery failures and the fleet route flag (#187).

Changed

  • Webhook delivery lists are paged (#191).
  • The Tenkai contract is pinned to the v0.9.0 release (#195). pnpm api:sync also accepts a full commit on Tenkai main (#154).

v0.4.0-rc.1

v0.4.0-rc.1 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 15 Nov 12:56
Immutable release. Only release title and notes can be modified.
v0.4.0-rc.1
c40bdf2

Release candidate for 0.4.0, the console for Tenkai 0.9.

Upgrade

Tenkai pins the console in ui/console.pin, which takes only final tags, so this candidate is for manual review; Tenkai pins v0.4.0. Rollback is pinning the previous zip.

The bundle still requires /healthz to list contract tenkai.http.v1. Types are generated from the signed Tenkai v0.9.0 schema. Against a 0.8 server, the screens for 0.9 routes read as unavailable, a bare-array delivery list reads as the whole list, and a hold by selector reads as refused. Same-origin and air-gapped operation are unchanged.

Added

  • Instance health with checks, observed time, and repairing checks (#155, #172).
  • Channel promotion policy status, soak detail, and pause/resume (#157, #171).
  • What blocks an instance's next change (#159).
  • Automatic environment holds and the failure threshold (#160), and hold by selector with a live match preview (#185).
  • Cancel a running apply, with the cancel outcome, skipped steps, and rollback hold (#162, #174).
  • Sealed secret age and rotation due (#165).
  • Advisory waivers on exposure findings, the waiver list, and grace periods (#166, #180).
  • Environment and release labels, view and edit (#170).
  • Owners and notification endpoints, with owner reachability and single product endpoint removal (#169, #182).
  • Rendered target changes and the approval brief on plans and approvals (#173, #175).
  • Health recall rule: recall details, measured shares, removal progress, and editing the rule (#176, #189).
  • Upgrade pace for a channel from Releases, pacing progress with early admit, and the configured pace next to the pace in effect (#178, #179, #184).
  • Attributed delivery failures and the fleet route flag (#187).

Changed

  • Webhook delivery lists are paged (#191).
  • The Tenkai contract is pinned to the v0.9.0 release (#195). pnpm api:sync also accepts a full commit on Tenkai main (#154).

v0.3.1

Choose a tag to compare

@github-actions github-actions released this 11 Nov 18:36
Immutable release. Only release title and notes can be modified.
v0.3.1
f327d6f

Upgrade

Tenkai pins the console in ui/console.pin. To serve this release, pin v0.3.1 with the SHA-256 of tenkai-console-v0.3.1.zip from SHA256SUMS. Rollback is pinning the previous zip.

The bundle still requires /healthz to list contract tenkai.http.v1. Types are generated from the signed Tenkai v0.6.0 schema. Same contract as 0.3.0.

Fixed

  • CycloneDX SBOM includes serialNumber, which GitHub SBOM attestation requires.

v0.2.0

Choose a tag to compare

@Sannrox Sannrox released this 07 Oct 09:44
3a7eb5e

Upgrade

Tenkai pins the console in ui/console.pin. To serve this release, pin v0.2.0 with the SHA-256 of tenkai-console-v0.2.0.zip from SHA256SUMS. It needs a server that serves contract tenkai.http.v1, the same contract as v0.1.0.

Added

  • Subscribe an environment to a product channel from Environments (#15).
  • Publish, promote, and recall releases from Releases. Signing stays outside the browser (#16).
  • Reconcile: request one tick from Delivery and see the server's per-environment report (#17).

Changed

  • Every management action asks for confirmation once, and the confirmation names exactly what will be sent. The server's message is shown as sent, and a lost response reads as unknown rather than success.
  • Each click sends one request with its own x-request-id, never retried.
  • After the server refuses the signed-in credential for an environment or for the fleet, that scope's controls are hidden for the rest of the session.

Fixed

  • A management click made while the browser was offline (approve, apply, plan, rollback, retire) was held and sent on reconnect. It is now refused immediately and shown as unknown.
  • README claims about /ui serving and same-origin requests (#14).

Known limits

  • Tenkai serves no listing of a caller's grants, so a read-only credential sees management controls until its first refusal.
  • There is no release listing route, so a recalled channel head still shows as the head until another release is promoted.

v0.1.0

Choose a tag to compare

@github-actions github-actions released this 01 Oct 15:25
cc0d7f8
feat: environments, releases and access pages (#12)

Decision 4D: Delivery, Releases, Environments and Access are routed top
tabs with no second menu. Environments lists every active environment
(channels, deployed count, facts, lease, latest plan) with the selected
row's subscriptions, facts, lease, a link to its plan, and retire with a
required reason. Releases shows each product's channel heads and which
environments follow them. Access shows the signed-in identity and method.
One signed-in layout now owns the sign-in gate, expired and no-access
states and the top bar for every page.

Maintenance windows and constraints are not served by inspect yet
(Sannrox/tenkai#477), so those 4D columns wait for it.

Closes #4

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>