Skip to content

chore: move to harmont-cloud 0.2 (/api/v1)#159

Merged
markovejnovic merged 1 commit into
mainfrom
chore/harmont-cloud-0.2-api-v1
Jul 6, 2026
Merged

chore: move to harmont-cloud 0.2 (/api/v1)#159
markovejnovic merged 1 commit into
mainfrom
chore/harmont-cloud-0.2-api-v1

Conversation

@markovejnovic

@markovejnovic markovejnovic commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

No description provided.

The Harmont REST API is cutting from /api/v0 to /api/v1. harmont-cloud 0.2.0
carries the new prefix and the v1 model shapes; bump both SDK pins and migrate
the cloud watch/whoami paths to them:

- watch.rs: the v1 SDK renames `models::Job` → `HarmontJob` and exposes a job's
  primary key as the string `id` (was a `Uuid`). Parse `job.id` into the `Uuid`
  that `BuildEvent`/step maps key on, at the SDK boundary. Job/build state is
  now the forward-compatible `OpenJobState`/`OpenBuildState`; `job_logs_available`
  matches `OpenJobState` (an `Unknown` future state streams rather than dropping
  its logs) and the terminal checks take the open enums directly. `started_at`/
  `finished_at` are now RFC 3339 strings — parse them for the step duration.
- whoami.rs: current-user id field `uuid` → `id`.

Requires harmont-cloud / harmont-cloud-raw 0.2.0 on crates.io; the Cargo.lock
bump lands with `cargo update` once those are published.
@markovejnovic markovejnovic merged commit baf0740 into main Jul 6, 2026
2 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant