Update the kitchenowl flake input to 0.8.1 #56

Closed
opened 2026-11-10 19:47:06 +00:00 by martin · 1 comment
Owner

Summary

The deployed kitchenowl backend is 0.7.10 because flake.lock still pins the input at 25eecca. Upstream main is 541ef29 (KitchenOwl 0.8.1), on both the Forgejo repository and the Codeberg mirror.

Context

  • Running unit uses /nix/store/y275k8j1a5gd7f29p082b13h0saa1wvf-kitchenowl-backend-0.7.10.
  • 0.8.1 store paths already exist locally from an earlier build.
  • The module runs Flask migrations in ExecStartPre, so no manual migration step is expected.
  • 0.8.1 does not fix the warnings tracked elsewhere (collation, autoflush, malformed JSON).

Scope

  • Update the input, rebuild, deploy, and verify the service and its migrations.

Acceptance criteria

  • just update kitchenowl updates flake.lock to 0.8.1.
  • just build nidaros succeeds.
  • Deployed backend reports 0.8.1 (systemctl show kitchenowl-backend -p ExecStart).
  • kitchenowl-backend is active with no migration errors in the journal.
## Summary The deployed kitchenowl backend is 0.7.10 because `flake.lock` still pins the input at `25eecca`. Upstream `main` is `541ef29` (KitchenOwl 0.8.1), on both the Forgejo repository and the Codeberg mirror. ## Context - Running unit uses `/nix/store/y275k8j1a5gd7f29p082b13h0saa1wvf-kitchenowl-backend-0.7.10`. - 0.8.1 store paths already exist locally from an earlier build. - The module runs Flask migrations in `ExecStartPre`, so no manual migration step is expected. - 0.8.1 does not fix the warnings tracked elsewhere (collation, autoflush, malformed JSON). ## Scope - Update the input, rebuild, deploy, and verify the service and its migrations. ## Acceptance criteria - [ ] `just update kitchenowl` updates `flake.lock` to 0.8.1. - [ ] `just build nidaros` succeeds. - [ ] Deployed backend reports 0.8.1 (`systemctl show kitchenowl-backend -p ExecStart`). - [ ] `kitchenowl-backend` is active with no migration errors in the journal.
Author
Owner

Progress

KitchenOwl is now pinned to the v0.8.1 release tag and deployed on nidaros.

  • flake.nix: url = "git+https://code.martials.no/martin/kitchenowl-flake?ref=refs/tags/v0.8.1".
  • flake.lock: refs/tags/v0.8.1, rev a19d87e (annotated tag object pointing at commit 541ef29), URL moved from Codeberg to code.martials.no.
  • Backend and web both evaluate to 0.8.1.
  • just build nidaros succeeded; the closure diff shows kitchenowl-backend and kitchenowl-web 0.7.10 -> 0.8.1, SQLAlchemy 2.0.49 -> 2.1.8, and added psycopg/psycopg-c.
  • Activated on nidaros at 2026-11-10 21:31 CET. Alembic migration 0b10d67750be -> ff57ce339705 ran in ExecStartPre, and kitchenowl-backend.service is active with kitchenowl-backend-0.8.1.

The known warnings persist and are tracked elsewhere: null item_id requests from the Android client, malformed JSON 500s (#15), and the autoflush SAWarning (#16). The collation repair (#55) is still pending.

The flake change is staged in the working tree but not committed yet.

## Progress KitchenOwl is now pinned to the `v0.8.1` release tag and deployed on nidaros. - `flake.nix`: `url = "git+https://code.martials.no/martin/kitchenowl-flake?ref=refs/tags/v0.8.1"`. - `flake.lock`: `refs/tags/v0.8.1`, rev `a19d87e` (annotated tag object pointing at commit `541ef29`), URL moved from Codeberg to `code.martials.no`. - Backend and web both evaluate to `0.8.1`. - `just build nidaros` succeeded; the closure diff shows `kitchenowl-backend` and `kitchenowl-web` 0.7.10 -> 0.8.1, SQLAlchemy 2.0.49 -> 2.1.8, and added `psycopg`/`psycopg-c`. - Activated on nidaros at 2026-11-10 21:31 CET. Alembic migration `0b10d67750be -> ff57ce339705` ran in `ExecStartPre`, and `kitchenowl-backend.service` is active with `kitchenowl-backend-0.8.1`. The known warnings persist and are tracked elsewhere: null `item_id` requests from the Android client, malformed JSON 500s (#15), and the autoflush `SAWarning` (#16). The collation repair (#55) is still pending. The flake change is staged in the working tree but not committed yet.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Personal/nixos-configuration#56
No description provided.