From 22c876f133c384480f0d49eb97c6e75d4747d684 Mon Sep 17 00:00:00 2001 From: Jeremy Daer Date: Wed, 16 Sep 2026 22:14:48 -0700 Subject: [PATCH] Say which SDK release the pin is, now that it is one The SDK version note still explained that the pin could not be a release tag because the event-feed operations were unreleased. They shipped in v0.19.0, and go.mod has named that tag since #729, so the paragraph described the opposite of what the file two directories over says. --- API-COVERAGE.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/API-COVERAGE.md b/API-COVERAGE.md index 976a74500..c42c64a97 100644 --- a/API-COVERAGE.md +++ b/API-COVERAGE.md @@ -49,11 +49,9 @@ Out-of-scope sections are excluded from parity totals and scripts: chatbots (dif > Note: the per-row `Endpoints` column in the Coverage by Section table sums higher than the Summary totals above. The discrepancy predates the BC5 baseline; the row count (48 sections) is authoritative for the `Since` column. Reconciling endpoint counts is pre-existing maintenance, tracked separately. **SDK version:** the pin in `go.mod`, with -`internal/version/sdk-provenance.json` authoritative for the exact commit. The -event-feed operations are unreleased, so that pin is a basecamp-sdk `main` -pseudo-version rather than a release tag; it builds on v0.18.0, the latest -release. The -command surface below largely dates to the v0.12.0 bump, which added 20 exported +`internal/version/sdk-provenance.json` authoritative for the exact commit. That +pin is basecamp-sdk v0.19.0, the release that ships the event-feed operations. +The command surface below largely dates to the v0.12.0 bump, which added 20 exported Go methods over 13 new backend operations; the extra seven wrapped endpoints that already existed but were reachable only through the raw generated client, which the andon-cord rule forbids the CLI from calling. v0.13.0–v0.15.0