v0.74.0 Release Recap

v0.74.0 is a non-breaking backup operations release that adds durable receipts for executed published backup catalog repairs.

What's New

Area	New in v0.74.0	Why it matters
Publish repair evidence	--receipt-out PATH	Records what catalog metadata was written during an executed lifecycle index publish
Receipt content	Endpoint, method, status, response, payload hash, and payload	Gives operators reviewable evidence after replacing published backup catalog metadata
Repair guard docs	Receipt step added to the execution flow	Keeps repair evidence beside the dry-run, drift, and freshness checks
Feature metadata	published-backup-repair-receipt	Lets live deployments advertise publish repair receipt support

Operator Flow

Run the publish command as a dry run first:

contextdb snapshot lifecycle index publish \
  --in "$CONTEXTDB_BACKUP_DIR/contextdb-backups.index.json" \
  --publish-url "$CONTEXTDB_LIFECYCLE_INDEX_PUBLISH_URL" \
  --report

After the repair guard checks pass, execute with a receipt:

contextdb snapshot lifecycle index publish \
  --in "$CONTEXTDB_BACKUP_DIR/contextdb-backups.index.json" \
  --publish-url "$CONTEXTDB_LIFECYCLE_INDEX_PUBLISH_URL" \
  --execute \
  --token "$NORN_TOKEN" \
  --receipt-out "$CONTEXTDB_BACKUP_DIR/published-backup-repair.receipt.json" \
  --report

Then rerun drift and freshness checks before closing the incident.

Compatibility

This release is intentionally non-breaking. The receipt is opt-in and only writes when paired with --execute; existing dry-run and publish behavior is unchanged when --receipt-out is omitted.

Verification

Release verification included:

go test -count=1 ./cmd/contextdb
go test -count=1 ./...
npm run docs:build
git diff --check

Read the full workflow in the Published Backup Repair Guard.