v0.2.1

What's Changed

The transitional option --enable-v1seals has been removed. All seal related behaviour is automatic now.

The replicate-logs command fixes an issue that could prevent continued local replication. The state is recoverable. If you are seeing replication failures due to cbor length, please contact support for remediation.

The watch command includes fixes for incorrect handling of the --horizon paramater. It also supports --latest as an alias for "show me the most recent change for all selected tenants"

• Fix tail seal output by @landintrees in #37
• fix: horizon commanline option parse issues by @robinbryce in #38
• Dev/robin/10146 make v1seals the default by @robinbryce in #39
  • Note: go-datatrails-merklelog v0.2.3 includes the fix for the replication issue. This PR bumps veracity to consume that version.

New Contributors

• @landintrees made their first contribution in #37

Full Changelog: v0.2.0...v0.2.1

v0.2.0

What's Changed

Quality of life changes to replicate logs, a new receipt command for COSE Receipts, v1 seal support (has to be explicity requested)

replicate-logs

• Graceful handling of ratelimiting errors with automatic retries
• --latest flag to automatically discover the latest log state. This eliminates the need to pipe in the output of the watch command
• Support for transition to v1 (from v0) checkpoint format. Seals for massifs which are full will not change. Seals for any open massifs will be upgraded to v1 format. The log data format has not changed in anyway. With this release --enable-v1seals is required to enable this behaviour. This is transitional support. This release precedes enabling v1 seals in the service. --enable-v1seals is provided to ease transition testing and will be removed in a subsequent release. The behaviour described here is then automatic.

receipt

New command, enabled for testing purposes in this release. Only works if the --data-url referenced service has v1 seal support.

This command generates receipts according to the ietf drafts:

• https://datatracker.ietf.org/doc/draft-ietf-cose-merkle-tree-proofs/
• https://www.ietf.org/archive/id/draft-bryce-cose-merkle-mountain-range-proofs-00.html

Changes

• fix: handle 429 errors gracefully, with re-tries, in replicate-logs by @robinbryce in #33
• add --latest mode for replicate-logs by @robinbryce in #36
• tests: add coverage for verifying inclusion against massifs after the… by @robinbryce in #31
• feat: multi massif test for node command by @robinbryce in #32
• Support for COSE Receipts (MMRIVER) by @robinbryce in #34
• enable release of veracity ahead of production v1 seals by @robinbryce in #35

Full Changelog: v0.1.4...v0.2.0

v0.2.0-pre0

COSE Receipts release

Alignes with the new forestrie checkpoint seal format from https://github.com/datatrails/go-datatrails-merklelog/releases/tag/mmr%2Fv0.1.0

This release updates replicatelogs to safely accomodate the current v0 seal format and the new v1 seal format

Historic log seals for complete massifs will not change.

For replicas where the last massif is "open" (is not full), the seal for that last massif will be promoted to the new format if the remote is on the v1 seal format.

For this release only --enable-v1seals is required to accept seals in the new format. veracity will stop replication if it encounters a remote seal in the v1 format when this flag is not set.

Once forestrie is released, this flag will be removed and its behaviour will be the default.

What's Changed

• tests: add coverage for verifying inclusion against massifs after the… by @robinbryce in #31
• feat: multi massif test for node command by @robinbryce in #32
• fix: handle 429 errors gracefully, with re-tries, in replicate-logs by @robinbryce in #33
• Support for COSE Receipts (MMRIVER) by @robinbryce in #34

Full Changelog: v0.1.4...v0.2.0-pre0

v0.1.4

Full Changelog: v0.1.3...v0.1.4

fix: --version reports 'unknown'

v0.1.3

Full Changelog: v0.1.0...v0.1.3

• veracity replicate-logs --progress shows a progress meter on the terminal.
• veracity --version reports the version of the tool

Note: the gap in the patch releases, from v0.1.0 - v0.1.3 was due to release automation changes.

v0.1.0

What's Changed

• Dev/robin/9780 veracity update-replica command by @robinbryce in #26
• fix: snags and bugs revealed by docs writing by @robinbryce in #28
• Dev/robin/9874 systemtests for watch and replicatelogs by @robinbryce in #29

Full Changelog: v0.0.6...v0.1.0

v0.0.6

What's Changed

• Clean up command grouping in README by @wp0pw in #18
• Update the Readme by @SteveLasker in #20
• remove windows releases by @henry739 in #23
• Add system tests to veracity by @Serhiy1 in #21
• feat: console mode for watch command by @robinbryce in #24
• Incorporate PR20 feedback by @SteveLasker in #22
• feat: adds paging support for veractiy watch by @robinbryce in #25
• fix massif selection and peak stack init by @henry739 in #27

New Contributors

• @SteveLasker made their first contribution in #20
• @Serhiy1 made their first contribution in #21

Full Changelog: v0.0.5...v0.0.6

v0.0.5

What's Changed

• Dev/henry/9606 readme update by @henry739 in #17

Full Changelog: v0.0.4...v0.0.5

v0.0.4

What's Changed

• Update Readme with update verification default by @honourfish in #12
• use logverification event structures by @honourfish in #9
• Add offline mode by @wp0pw in #10
• remove arg0 file input and add validation by @henry739 in #13
• Dev/henry/9606 default to prod url by @henry739 in #15
• change envets-verify to verify-included by @wp0pw in #14
• Add VERACITY_IKWID for advanced commands by @wp0pw in #16

New Contributors

• @honourfish made their first contribution in #12
• @henry739 made their first contribution in #13

Full Changelog: v0.0.3...v0.0.4

v0.0.3

What's Changed

• Dev/robin/9587 support public and shared assets by @robinbryce in #7
• fix: README styling by @robinbryce in #8

Full Changelog: v0.0.2...v0.0.3