hero_os Cargo.lock: hero_osis_sdk pin predates ProjectStatus enum shrink #83

New issue

Closed

opened 2026-04-22 07:25:56 +00:00 by zaelgohary · 0 comments

zaelgohary commented

2026-04-22 07:25:56 +00:00

Member

hero_os Cargo.lock pins hero_osis_sdk at a commit whose ProjectStatus enum still has seven variants (Planning, Active, NotStarted, OnHold, Completed, Cancelled, …). A subsequent SDK commit shrank the enum to three values — Todo / InProgress / Done — and the osis server now writes the new values to disk.

When the WASM app fetches a project whose stored status is "todo", the old SDK fails to deserialize with invalid type: string "todo", expected variant Planning | Active | …. The UI surfaces this as "Method not found" on kanban task moves and on milestone creation.

Fix:

cargo update -p hero_osis_sdk
cargo update -p hero_archipelagos_projects  # re-pin archipelagos to a dev commit compatible with the new enum

Then rebuild + redeploy.

hero_os `Cargo.lock` pins `hero_osis_sdk` at a commit whose `ProjectStatus` enum still has seven variants (Planning, Active, NotStarted, OnHold, Completed, Cancelled, …). A subsequent SDK commit shrank the enum to three values — Todo / InProgress / Done — and the osis server now writes the new values to disk. When the WASM app fetches a project whose stored status is "todo", the old SDK fails to deserialize with `invalid type: string "todo", expected variant Planning | Active | …`. The UI surfaces this as "Method not found" on kanban task moves and on milestone creation. Fix: ``` cargo update -p hero_osis_sdk cargo update -p hero_archipelagos_projects # re-pin archipelagos to a dev commit compatible with the new enum ``` Then rebuild + redeploy.