Upgrade note for v4 CLI
Developers see concrete upgrade commands, API diffs, package status, and rollback instructions instead of a vague announcement.
ManifestRun turns every launch into a signed release packet: compatibility checks, package rollout gates, copy-ready changelogs, and live developer feedback in one inspectable surface.
First-viewport job: confirm whether this launch can go public.
Toggle the gates below. The deploy action stays disabled until the launch packet is complete.
Select a release phase to see the exact work ManifestRun packages for engineering, product, docs, and developer relations.
manifestrun freeze --api openapi.yaml --sdk npm:@acme/sdk --require-compatibleCopied
Generated launch pages include pass, hold, fail, loading, and empty states so the release story is honest even when one package lags behind.
| Target | Version | Status |
|---|---|---|
| npm @acme/cli | 4.0.0 | Pass |
| pip acme-sdk | 4.0.0rc2 | Hold |
| Homebrew tap | 3.9.8 | Blocked |
| Cargo crate | empty | No artifact |
| Surface | Finding | Owner |
|---|---|---|
| REST | Deprecated header removed from beta only | API |
| CLI | Flag alias retained for 90 days | Core |
| Docs | All snippets execute in CI | DX |
| Support | Escalation room pre-created | DevRel |
Developers see concrete upgrade commands, API diffs, package status, and rollback instructions instead of a vague announcement.
ManifestRun is built for teams whose users read changelogs, diff SDKs, pin package versions, and expect every launch claim to be reproducible.