Repository navigation
chore(sdk/go): remove the in-tree Go SDK after the final deprecated tag #5242
Description
Part of #5031.
After the Go SDK moved to ai-openshell/sdk-go and the in-tree module is deprecated, remove what is left of it from core.
Scope
- Delete
sdk/go/andtasks/go.toml, and the Go tools inmise.tomlandmise.lock. - Remove Go from CodeQL (
.github/workflows/codeql.yml,.github/codeql/codeql-config.yml). - Remove the
sdk/gotag workflows (.github/workflows/sdk-go-tag.ymland thetag-sdk-gojob inrelease-publish.yml). - Point
README.md,CONTRIBUTING.md,AGENTS.md,TESTING.md,docs/sdk/go.mdx, and thebuild-openshell-mxc-windowsskill at sdk-go. - Drop the Go SDK Freeze job from Branch Checks, since there is nothing left to guard.
When
After the first core stable release whose sdk/go/vX.Y.Z tag carries the deprecation comment, and after the sdk-go release automation is live. The tag stays, so existing consumers keep building and see the deprecation.
Activity
elezar commentedon Nov 4, 2026
Assessment: technically valid, but blocked. Part of #5031.
Verified against
main: every removal target still exists (sdk/go/,tasks/go.toml, Go tools inmise.toml, thegolanguage incodeql.ymlplussdk/goincodeql-config.yml,sdk-go-tag.yml, and thetag-sdk-gojob referenced at several points inrelease-publish.yml, including the required-jobs list). The Go SDK Freeze job does not exist yet because it comes from #5241.Gating conditions, none met yet:
go.mod, freeze job).sdk/go/vX.Y.Ztag carries the deprecation.When implementing, remember
release-publish.ymlreferencestag-sdk-goin itsneedslist and in the expected-jobs check, not only in the job definition.No User Story is present; this is a maintainer-authored chore tracked under #5031. No spike needed.
Next human decision: a maintainer to record disposition and keep this out of agent pickup until the gates above are met. I did not change labels:
state:validatedhas no description in the repo.