Upgrade from v0.6

The next minor release changes public model type identities. Rebuild your application and check interfaces, struct literals, and type assertions before upgrading from v0.6.0.

Model importsCopy Anchor Link

Use pkg/ring for client calls and public result types. Wire models live in pkg/dependencymodels/rest, pkg/dependencymodels/fcm, and pkg/dependencymodels/signaling. Public read models live in pkg/ringapimodels. Existing model names have compatibility aliases, but types moved between packages can require changes to your own aliases and interface implementations.

Low-level account eventsCopy Anchor Link

pkg/dependencies/websocket.EventConnection.ReceiveFrame now returns the typed event and its original JSON as json.RawMessage. Use the typed first result for known fields. Decode the second result only when you need unknown extensions:

frame, raw, err := connection.ReceiveFrame()
if err != nil {
    return err
}
var extensions map[string]any
err = json.Unmarshal(raw, &extensions)
if err != nil {
    return err
}
fmt.Println(frame.Kind, extensions)

The higher-level account event API keeps its map projection. See the account events guide for normal client usage.

Shared HTTP clientsCopy Anchor Link

The v0.7 client snapshots an injected *http.Client when ring.NewClient is created and reuses its Transport. A cookie jar already set on that client is rejected because one reusable Ring client can serve multiple accounts. Setting a jar on the supplied *http.Client later does not change the Ring client's snapshot.

Low-level REST clients also snapshot injected HTTP clients. If a REST client is configured with a cookie jar, client.ConfigurationError() returns a typed *rest.HTTPClientConfigurationError and requests fail with that cause. The HTTPClient() accessor returns a shallow copy, so changing its fields does not change the reusable client; its Transport remains shared.