A small standard for the last release

End well.

Give users dates, alternatives, migration help, security expectations, and a safe path to their data—before a project goes quiet.

Local onlyMachine-readableHuman-readable

01 / Describe the exit

Build the sunset plan

Blank support dates become explicit null values: no promise is better than an implied promise.

Project and timeline

Project name Project kind Current status Announcement date General support ends Leave blank for no promised date Security support ends Leave blank when none is offered Last supported release Final support or security contact

Where users should go

Alternative type Alternative name Alternative URL Migration guide URL Migration notes

Durable notice and archive

Notice path Keep the source available as a read-only archive

02 / Check the handoff

Readiness report

—

Waiting for a plan

Complete the builder or load a sample.

03 / Publish both

One plan, two audiences

The JSON file supports automation. The Markdown notice gives people a clear final answer.

sunset.json

Generate a valid plan to preview the manifest.

SUNSET.md

Generate a valid plan to preview the notice.

Say when

Separate announcement, support, security, shutdown, export, and deletion dates.

Show the exit

Name a maintained alternative and give users practical migration steps.

Leave a trace

Preserve source and a durable notice unless keeping the code online is actively harmful.