upgrade-platform
Move a product onto a newer Plenipo release deliberately: re-vendor the platform packages, bump the single version property, unwind the TODO(plenipo#N) shims whose requests that release closed, and prove the whole test ladder still passes before the PR opens. Upgrades are never automatic — one bad release must not break every product at once. USE FOR: consuming a platform release, retiring a shim after a request lands, recovering a product that has drifted versions behind. DO NOT USE FOR: filing a new request (../request-platform-change/SKILL.md) or platform-side triage (/steward:triage-requests).
- License
- MIT
Pinned to revision a2ee8094fc23, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.