RELEASE REPORT

One release report link. Every published version.

Keep the latest report at the link your team already uses. Save a fixed version for release reviews, handoffs, and later AI work.

ILLUSTRATIVE SAMPLE · THE REVIEW GAP

Publish a report without creating a new handoff every time.

This sample is a single uploaded HTML file. It shows the workflow shape; it is not a customer artifact or a production approval.

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, release record, or later AI task.

UPLOADED HTML SAMPLEOpen full sample

PUBLISHING SEQUENCE

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

01
Build the report as one HTML file
Keep the layout, charts, styles, and interactions in one uploaded file of up to 20 MB. Remote resources remain external runtime dependencies.
02
Publish the first report
The successful publish identifies the Slide, version, latest view URL, and fixed version.
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.
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.