Releases

What changed in each release of nucleate, the box recipe and the Watch API, newest first.

On this page

nucleate #

nucleate and nucleated are released together, in one archive per target. The newest is 0.3.0. Install it, or take any release from its releases page.

nucleate 0.3.0 #

19 November 2026

Added

  • Report to the AIP-style ingest routes.

nucleate 0.2.0 #

19 November 2026

Added

  • Build macOS archives for the Homebrew tap.

nucleate 0.1.0 #

19 November 2026

The first release.

The box recipe #

Each release of the recipe pins the release of nucleate it was tested with, so a new nucleate is followed by a new recipe. The newest is 0.3.0, and it is the one the installer downloads. Every release is on its releases page.

Box recipe 0.3.0 #

19 November 2026

Added

  • nucleate 0.3.0.

Box recipe 0.2.0 #

19 November 2026

Added

  • Release from main and attach the packed recipe.

The Watch API #

The API is described by one OpenAPI document, served at https://api.nucarium.com/openapi.json. These are the changes to it. The API reference always shows the newest.

Watch API 0.4.0 #

  • Breaking. Sign-in is with GitHub. AuthMode is github or dev; the clerk value is gone. Nothing changes for a box: nucleate login and the two ingest methods are as they were.
  • Me.user now carries the person's GitHub login and name beside id and email, and Me.role says whether they own the account or are a member of it. Whoever signs up gets an account of their own and is its owner.
  • DELETE /v1/account answers forbidden to anyone but an owner, and takes what Watch knew about the account's people with it.
  • A person and their account are made when they sign in, and at no other time. A signed-in operation answers unauthorized for a person Watch does not know, and keeps nothing about them. That is everyone who has not signed in, and everyone whose account was deleted: DELETE /v1/account ends their sessions, and signing in again starts a new, empty account.
  • Me.user.login, name and email are what GitHub said when the person last signed in. They change at the next sign-in and not before.
  • The limit on trying user codes counts per account and per address of the owner's browser.

Watch API 0.3.0 #

  • Breaking. Actions are now custom methods in the AIP-136 style, with :verb after the resource id in place of a /verb segment: POST /v1/device-authorizations/{user_code}:approve, POST /v1/device-authorizations/{user_code}:deny and POST /v1/alert-destinations/{destination_id}:test. The old paths are gone. Requests and responses are unchanged.
  • Breaking. Revoking a machine token is a custom method too: POST /v1/machines/{machine_id}/tokens/{token_id}:revoke replaces DELETE /v1/machines/{machine_id}/tokens/{token_id}. A revoked token is not deleted: it stays in the list, marked revoked. The response is unchanged.
  • Breaking. The two ingest methods are custom methods on their collections: POST /v1/heartbeats:ingest replaces POST /v1/ingest/heartbeat, and POST /v1/events:ingest replaces POST /v1/ingest/events. Requests and responses are unchanged. A machine token is accepted on those two and nowhere else, as before.
  • The OAuth endpoints under /v1/oauth are unchanged. They keep the paths their RFCs give them.