tasks update --due= does not clear the due date

[alexph-dev]

Description

gog tasks update <listId> <taskId> --due= --force does not clear the due date on a task, despite the help text stating "set empty to clear".

Steps to Reproduce

1. Have a task with a due date set
2. Run: gog tasks update <listId> <taskId> --due= --account <email> --force
3. Observe the due date is unchanged

Expected Behavior

The due date should be cleared (set to null via the Google Tasks API PATCH with {"due": null}).

Actual Behavior

The due date remains unchanged. The command returns successfully and shows the old due date.

When using --json output on the update response, the due field shows null — but subsequent gog tasks list confirms the original due date is still set. This suggests the empty value may be omitted from the PATCH request body rather than being sent as an explicit null.

Environment

• gog version: v0.12.0 (c18c58c 2026-03-09)
• OS: Linux 6.8.0 x86_64
• Installed via: brew (steipete/tap/gogcli)

Workaround

Currently setting --due 2099-12-31 as a workaround.