Release notes
Read dated CLI and private Framework changes, their separate identities and the applicable update guidance.
Match notes to your artifacts
CLI and Framework releases are independent. The entries below are dated records, not a live latest-version feed. Check the installed CLI and your retained Framework identity before applying release guidance.
Recorded changes — 22 October 2026
CLI 0.0.17 adds project-local versioned acquisition, shorter vendor folders, six retained Framework skills and concise command-family help. All five native qualification profiles passed. A separate post-publication Windows installation was not rerun; private writes and native project checks remain unavailable on Windows.
The matching private Framework RC2 contains 36 packages, three Starters, six skills and the Figma library. Source and package assets must share the same exact release identity. Octane 0.13.8 hydration limitations remain documented and releaseReady remains false.
Earlier changes — 15 October 2026
CLI 0.0.16 updates the licensing contact in the executable and notices. It retains the Framework acquisition, Recipe creation and local inspection workflows; it does not grant access to the paid Framework.
CLI 0.0.15 corrected RC2 reading and default private-release selection after the earlier acquisition failure. Use a compatible binary for the exact release format, rather than renaming tags or editing inventories to satisfy an older reader.
Framework 0.1.0 RC2, producer efdd12f carries the updated licensing contact in selected source and package licenses. It retains 29 packages, three Starters and five Framework skills. This private candidate remains releaseReady: false; access requires separate entitlement. Source and package assets must come from the same exact release.
Read the scope, not just the version
Public CLI availability is not commercial Framework support approval. The recorded 0.0.15 and 0.0.16 releases have native-platform exceptions; known Octane hydration and experimental GPU limits are not removed by the contact update. Use the release's own evidence and the current compatibility page for the applicable lane.
The historical 0.1 public preview describes older registry artifacts, not the current private package selection. Its availability and licensing history must not be applied to newer commercial source.
Find the update procedure
Updates and rollback owns application package switching and recovery. Framework releases owns acquisition and verification; Install the CLI owns executable installation. Framework updates never regenerate your adopted application source.