Shiplog

Releases

See every release,
and why.

Each release in this browser — Completed, Planned, or Cancelled — newest first, with its linked decisions. Expand a release to review each linked decision and its status.

Open the form to record a release Go to the deployment check

Release log

Copies the releases shown, in the order shown, with their linked decisions, as plain text for email or planning documents. Example records and records added in this browser are labeled separately.

Copy becomes available when releases are shown.

Use ↑ and ↓ to move between releases, Home and End to jump to the first and last release, Space to expand a release in place, and Enter to open its details page.

Loading releases…

Record a release

The version or tag for this release, such as v1.4.0.
Completed: ship date. Planned: planned ship date. Cancelled: cancellation date. Enter the status date as YYYY-MM-DD.
The person accountable for this release.
A short name for the release. Defaults to the version.
Completed means the release shipped. Planned means the release is intended to ship in the future. Cancelled means the release will not ship. The status describes the release, not the decisions linked to it.
What shipped, what is planned to ship, or why the release was cancelled, in a sentence or two.
Linked decisions (optional)

Link decisions to this release, or leave all unchecked. A decision can be linked at any status — Proposed, Pending, Accepted, or Superseded. Linking records the association only; it does not mean the decision was accepted or implemented. The first decision you tick gets its own section on the release page; the other linked decisions appear below it. Tab moves through the list; Space ticks or clears the decision in focus.

No decisions can be linked until the list loads.

A release you record here is kept in this browser, on this device: it is not sent to the Wawalu team, and a teammate on another browser or device will not see it. Use “Export shown releases as JSON” above to take your releases elsewhere.

Deployment record

The deployment record identifies the build expected to be live: the recorded build. The running build is the build currently served by this site. Release-log entries can be planned, completed or cancelled; they do not necessarily represent production deployments.

Loading the deployment record.

Deployment check

The deployment check compares the recorded build with the running build. Confirmed: the running build matches the recorded build.

Not a match: the running build differs from the recorded build. See the deployment record for the recorded build. Did not complete: this page cannot confirm whether the running build matches the recorded build. Check again later.

Checking…

Checking the running build against the recorded build: the result appears here in a few seconds.

From decision to release

Example records

These example records are invented: no such decision or release shipped. They use no customer or production data. Open either link below to read the full record: the decision’s context, or the release and its linked decisions.

Linked decision
Adopt a durable job queue
Decision owner
Kai
Decision status
Accepted
Completed release
v1.3.0 · Throughput and latency
Version
v1.3.0
Release status
Completed
Release owner
Kai
Summary
Throughput and latency
Open this example release

Real decision from Shiplog's repository

Real decision

This decision comes from Shiplog’s own public development history. It is not invented, and not data from any team using Shiplog.

Checking this decision against the repository record.

Decision
Mark every record row with whose record it is
Decision status
Accepted
Decision owner
Mina
Source repository
AndrewLikesTea/wawalu-agent-lab on GitHub
Recorded build
Commit 28b2398ff49c, which merged pull request #2547

Last verified 25 September 2026.

This describes a recorded build, not the deployment running now.

Open pull request #2547, the source of this decision, on GitHub Open commit 28b2398ff49c, the recorded build, on GitHub Inspect the recorded build stamp on GitHub

Try the whole demo in four steps

  1. Step 1 of 4 · Do this now Record a decision with the decision form on the Home page.
  2. Step 2 of 4 · Not started Arrive here with that decision ready to link.
  3. Step 3 of 4 · Not started Record a release on this page and link that decision to it.
  4. Step 4 of 4 · Not started Open the release you recorded and check its summary and linked decision.

No decision is recorded in this browser yet, so there is nothing to link to a release here. Step one is the decision form on the Home page.

Open the decision form on the Home page

Records you add stay in this browser unless you download the complete archive, which sends them to the Shiplog server to build the file. This is a demo workflow, not a customer result.

Send a Shiplog follow-up request

Send a Shiplog follow-up request, and a person on the Wawalu team that operates it replies by email, usually within two working days.

Request a Shiplog demonstration Discuss a Shiplog pilot

Choose a discussion topic in the follow-up form below, then add your work email and an optional note. There is no self-serve signup and no published price. Whether Shiplog is available for your team and what it would cost are both answered on request.

Releases on this page that link a decision

Still counting the releases loaded in this browser: how many of them link at least one decision the decision log holds, out of how many were loaded.

A release is covered when it links at least one decision the decision log holds; every other release is uncovered.

Both numbers are over every release loaded on this page, not the filtered view: the search and the filters do not change them.

Coverage count still in progress.

The copy control becomes available once the figures are counted.