Bump the SDK to 0.8.0

[robzolkos]

Release prep for the typed collection-detail operation in #97, now that the Haystack endpoint is deployed and the SDK change is merged.

This is a minor bump because the release adds the public GetCollection generated operation plus CollectionsService.Get and GetPage. Existing SDK callers remain compatible.

APIVersion stays at 2026-08-21; this PR changes only the SDK Version sent in the User-Agent from 0.7.0 to 0.8.0.

Validation

• mise exec -- env GOWORK=off make go-check — passed
• make bump VERSION=0.8.0 — changed only go/pkg/hey/version.go
• The local full gate reached the existing generated-client retry conformance instability tracked by Honor per-operation retry policies in the generated client #94; no failure involved the version change. Current-head GitHub CI is the full-gate evidence for this one-line bump.

After this merges, make release VERSION=0.8.0 will run the release gate and create both v0.8.0 and go/v0.8.0.

Collection SDK card: https://app.basecamp.com/2914079/buckets/48521764/card_tables/cards/10225277027

---

Summary by cubic

Bumps the HEY Go SDK version from 0.7.0 to 0.8.0 to publish the typed collection-detail API. Previously the SDK sent User-Agent version 0.7.0; now it sends 0.8.0. APIVersion remains 2026-08-21.

• Single-line change in go/pkg/hey/version.go; no behavior change beyond the reported SDK version.
• 0.8.0 includes the generated GetCollection operation and CollectionsService.Get / CollectionsService.GetPage; no migrations required.
• After merge: run make release VERSION=0.8.0 to publish v0.8.0 and go/v0.8.0.

^{Written for commit 76ba069. Summary will update on new commits.}

[Copilot]

Pull request overview

Bumps the Go SDK release version to 0.8.0, exposing the collection-detail functionality added in #97.

Changes:

• Updates the SDK version reported in the default User-Agent.
• Keeps APIVersion unchanged.

Tip

If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.