Skip to content

tabc 0.2.4

Latest

Choose a tag to compare

@jultabc jultabc released this 25 Oct 07:36
e45acb0

Changes

  • Add tabc send --id <UUID> for retries using a caller-saved message ID. After normal send checks pass, an identical request is not stored twice. Changed content or recipients produce a conflict.
  • Keep the existing behavior when --id is omitted: each send receives a new random ID. The local MCP adapter already supports message_id; this release adds the CLI option.
  • Link the PyPI introduction to the GitHub changelog, published releases, and upgrade instructions.
  • Make the process-argument test wait briefly for a newly started child process. Product validation remains unchanged.

Upgrade

See Upgrading from 0.2.3 to 0.2.4.

The new CLI option works with an existing 0.2.3 daemon. This feature does not require a ledger conversion or node re-registration. Follow the documented backup and stop/install/restart procedure when replacing the complete running installation.

Duplicate-storage prevention is not a read receipt or a guarantee that a task ran once. Preserve the ID and complete message inputs before the first attempt. Read-before-send and other normal send checks still apply.