[bfrancojr]

Fixes #53.

What changes

alidade now depends on a released caliper. Since PR #44, go.mod had pinned caliper to an unreleased commit (c88a51b, the KeepWhenAllFail change for #41) as a pseudo-version. It now requires caliper v1.7.0, which you authorized me to release:

• I merged changelog: the Unreleased section is v1.7.0, released 2026-10-18 trendvidia/caliper#50 (changelog) as 7a1a643;
• annotated tag v1.7.0 on 7a1a643;
• release published.

v1.7.0's code is the pinned commit's plus a two-line changelog edit, so alidade builds the same caliper code as before.

Evidence

• go.mod and go.sum: only caliper's lines change, from the pseudo-version to v1.7.0. go mod tidy is clean.
• THIRD_PARTY_NOTICES.txt: regenerated with GOROOT=~/projects/src/github.com/trendvidia/go go run scripts/notices.go. Only caliper's version line changed. -check exits 0.
• go test -count=1 -tags v8,python ./... with CGO_ENABLED unset: 20 packages ok, exit 0.
• golangci-lint run ./...: 0 issues.

caliper's release workflow, which attaches the binaries, was still running when I opened this. alidade doesn't depend on those binaries.

[bfrancojr]

CI on 6aa7533: golangci-lint, linux and macOS vet + build + test all pass. caliper's release workflow for v1.7.0 succeeded and attached 13 assets, the same set as v1.6.2 (12 binaries plus checksums.txt). Ready for your merge.