kolaenteandkolaente 7691f282cf fix(veans): preserve unsent task fields on update via PATCH (#2962) ...

The v1 update was a whole-object POST /tasks/{id}: omitted scalars were
zeroed, so a status-only `veans update` silently wiped a task's
description and priority. The v1->v2 migration replaced that with
PATCH /tasks/{id} carrying a JSON Merge Patch built from only the
changed fields (client.TaskPatch, all-pointer + omitempty), which fixes
this by construction — absent fields are left untouched server-side.

Pin it with the acceptance tests from the issue: a title-only and a
status-only update must send only the field(s) they change, so the
stored description and priority survive.

2026-06-26 11:23:14 +00:00

..

auth

test(veans): cover bootstrap validators and prompt UX

2026-05-27 08:21:57 +00:00

bootstrap

refactor(veans): migrate API client from v1 to v2

2026-06-26 11:23:14 +00:00

client

refactor(veans): migrate API client from v1 to v2

2026-06-26 11:23:14 +00:00

commands

fix(veans): preserve unsent task fields on update via PATCH (#2962)

2026-06-26 11:23:14 +00:00

config

feat(veans): make the HTTP client timeout configurable via .veans.yml

2026-05-27 08:21:57 +00:00

credentials

test(veans): cover credential-store hardening invariants

2026-05-27 08:21:57 +00:00

output

test(veans): cover the stable error-envelope contract

2026-05-27 08:21:57 +00:00

picker

feat(picker): add hierarchical fuzzy project picker

2026-06-10 13:51:46 +02:00

status

feat(veans): make the HTTP client timeout configurable via .veans.yml

2026-05-27 08:21:57 +00:00