Skip to content

docs(publish): record the first Go SDK release (sdk/go/v0.1.0) #72

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
macanderson merged 1 commit into from
Aug 1, 2026
Merged

docs(publish): record the first Go SDK release (sdk/go/v0.1.0) #72

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,8 +26,16 @@ which. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1
build`, `twine check`, `twine upload`). Verified against the *published*
package, not the checkout: `pip install contextgraph-sdk` into a scratch
venv, then the example provider run from that venv passes all 13 checks in
`conformance-external.sh` — the #59 acceptance bar. The Go module publish
(a `sdk/go/v0.1.0` tag) remains the one still-unpublished SDK.
`conformance-external.sh` — the #59 acceptance bar.
- **First Go SDK publish** (2026-08-01) — tag `sdk/go/v0.1.0` is pushed (on
green main, `4377bff3`), which for a Go module *is* the publish. The first
`go get` was run deliberately to seed `proxy.golang.org`/`sum.golang.org`
(per [sdk/PUBLISHING.md](./sdk/PUBLISHING.md)); a scratch module resolves
`github.com/macanderson/context-graph-protocol/sdk/go v0.1.0` with a
recorded `go.sum` checksum, and the example provider built against the
externally-fetched module — not the checkout — passes all 13 checks in
`conformance-external.sh`. The tag-triggered `verify-go` job is green. All
three SDKs and all three crates are now published.
- **Conformance registry + provider badge** (`docs/registry.md`,
`assets/badges/conformant.svg`, #20) — a page listing providers that are green on
`contextgraph-conformance`'s suite, each backed by a reproducible
Expand Down
9 changes: 5 additions & 4 deletions sdk/PUBLISHING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,11 +13,12 @@ green on `.github/scripts/conformance-external.sh` — before anything goes out.
| --- | --- | --- |
| TypeScript | npm, `@contextgraphprotocol/typescript-sdk` | ✅ published (PR #46) |
| Python | PyPI, [`contextgraph-sdk`](https://pypi.org/project/contextgraph-sdk/) | ✅ published 0.1.0 (2026-07-31) |
| Go | Go module proxy, `.../sdk/go/contextgraph` | ⬜ not yet published (tag-gated, see below) |
| Go | Go module proxy, `.../sdk/go/contextgraph` | ✅ published 0.1.0 (2026-08-01, tag `sdk/go/v0.1.0`) |

**Nobody has run the Go publish steps yet.** This file exists so the
*first* real publish of each is a checklist, not an improvisation — exactly
the role [`../PUBLISHING.md`](../PUBLISHING.md) plays for the crates.
**All three first publishes have now happened.** This file remains the
checklist for every *subsequent* release, so a version bump is a checklist,
Comment on lines +18 to +19

@sourcery-ai sourcery-ai Bot Aug 1, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion (typo): Wording of “first publishes” is awkward; consider a more natural phrase.

“First publishes” is an unusual noun phrase. Please reword this sentence for clarity, e.g., “All three initial publishes have now happened,” “All three first publications have now happened,” or “All three first releases have now happened.”

Suggested change
**All three first publishes have now happened.** This file remains the
checklist for every *subsequent* release, so a version bump is a checklist,
**All three initial publishes have now happened.** This file remains the
checklist for every *subsequent* release, so a version bump is a checklist,

not an improvisation — exactly the role
[`../PUBLISHING.md`](../PUBLISHING.md) plays for the crates.

## npm (already live — for the next bump)

Expand Down
8 changes: 1 addition & 7 deletions sdk/go/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,14 +11,8 @@ the same conformance suite that judges the Rust reference provider.

## Install

> **Not yet published.** Go modules publish by tag, and that tag
> (`sdk/go/v0.1.0`) has not been cut yet, so the command below does not
> resolve — see [`sdk/PUBLISHING.md`](../PUBLISHING.md) for the publish
> checklist and current status. Until then, `require` a pseudo-version
> pinned to a commit SHA, or vendor from a checkout.

```sh
go get github.com/macanderson/context-graph-protocol/sdk/go/contextgraph
go get github.com/macanderson/context-graph-protocol/sdk/go/contextgraph@v0.1.0
```

## Write a provider
Expand Down
Loading