Upgrading

Versions are tags on the public package. Pin one with from: and read what changed before you move.

0.7.0 broke everything before it

The client before it spoke JSON and built its own screens' state. This one speaks the wire contract and is handed a hub your app owns. Every method was renamed and every model type replaced. There is no shim, and 0.6.x does not talk to the current API at all.

Moving is about fifteen lines: delete the old integration and follow Start here again.

What a version number means here

• While the first number is 0, a middle-number release may break something. The release notes say what.
• The SDK and the server agree on one contract, and each checks its own pin, so a version that could not talk to us does not ship.
• A tag never moves. The commit a version points at today is the one it pointed at when it was published.

Staying on an old one

Nothing is switched off under you. An old build keeps calling the API it was built against, which is why the address a shipped app uses is kept alive rather than retired.