v0.5.0

Document metadata in responses is always tagged

Follows grepvine#152: the API now uses separate types for metadata you send and metadata you get back.

• Requests (Metadata): values can be plain strings, booleans and integers, or tagged {"type", "value"} objects. gv put -m NAME=VALUE, -m NAME:TYPE=VALUE and --metadata-file work the same as in v0.4.0.
• Responses (TaggedMetadata): every value is tagged with its type (string, integer, number, boolean, timestamp). gv list --json returns each document's metadata in this form.

Changes

• Read listing metadata as TaggedMetadata (#30). gv sync reads a document's tagged mtime directly. The wire format hasn't changed, so this release works with any server that serves typed metadata.
• Update the API snapshot from Grepvine 4ea20c3.
• Stop tracking the built gv binary (#29).

Upgrading

If you read gv list --json output, expect every metadata value as {"type": ..., "value": ...}, never a bare string or number.

Changelog

• 68410fb: Read listing metadata as TaggedMetadata (#30) (@nopcoder)
• f45f53d: Stop tracking the built gv binary (#29) (@nopcoder)
• d58d3c2: Update API snapshot from Grepvine 4ea20c36e631fa1e74a0e4862c26d996ac260771 (@github-actions[bot])