LedgerInfra
Menu

RELEASE REPORT

Give a living release report a stable review URL.

Publish one self-contained report, update the same Slide as release facts change, and keep every fixed version available for an exact handoff.

Open the Quickstart

THE REVIEW GAP

Publish a report without creating a new handoff every time.

Without a review artifact
A dated file or one-off URL makes readers ask which report is current, while overwriting the only copy removes the state used in an earlier handoff.
With the versioned workflow
The latest URL stays useful for the living report. Each publish also has a fixed version URL for the exact report state used in a review or release record.
Back to all examples
SELF-CONTAINED HTML SAMPLEOpen full sample

PUBLISHING SEQUENCE

One artifact. Four explicit decisions.

led publish ./release-report.html --title "Release Report" --json
  1. 01

    Build the report as self-contained HTML

    Keep the layout, charts, styles, and interactions inside one file of up to 20 MB.

  2. 02

    Publish the first report

    The successful publish identifies the Slide, version, latest view URL, and fixed version.

  3. 03

    Publish the next state

    Use --slide <SLIDE_KEY> for the revised report so the shared latest URL continues to resolve to the newest version.

  4. 04

    Use the right link for the job

    Share latest for ongoing review and fixed for a release note, audit record, or exact later reference.