Skip to content

fix(deps): move every Go service to sdk-go v0.3.2 so the host starts inside a composition - #1095

Merged
antoinetoussaint-byte merged 1 commit into
mainfrom
deps/sdk-go-v0.3.2
Oct 12, 2026
Merged

antoinetoussaint-byte merged 1 commit into
mainfrom
deps/sdk-go-v0.3.2

Conversation

@antoinetoussaint-byte

Copy link
Copy Markdown
Contributor

Moves the five Go services (accounts, auth-gateway, policy-log, store, telemetry) from sdk-go v0.3.1 to v0.3.2.

Why. With v0.3.1, a service resolves its own endpoint from the first workspace file above the process. When the host runs from its checkout, or from a released tag in the module cache, inside a larger composition, that file is the host's own development workspace, which names the module differently from the composition. telemetry and accounts then exit at start (cannot find module <saas> in <saas-starter-dev>). v0.3.2 (codefly-dev/sdk-go#68, closing sdk-go#66) trusts a found workspace only when it is the composition named by the injected CODEFLY__WORKSPACE; otherwise it reads the carrier the CLI injected. sdk-go#68 records the boot proof with this host's v0.0.94 tag: telemetry, accounts, auth-gateway and frontend reach Running, from both the checkout and the module cache.

Changes

  • go.mod/go.sum in the five services: sdk-go v0.3.2. go mod tidy drops indirect requirements v0.3.2 no longer needs.
  • accounts/code/fixtures/seed.go: codefly.Fixture() becomes fixture.Selected(), the API sdk-go#65 moved it to. Without it, accounts does not compile on any sdk-go after Generate ambient authorization for internal topology edges #65.

Classification: a fix, at the owner (dependency bump plus the API move it requires). Nothing was reinvented.

Verified locally (GOWORK=off, Go 1.27.2): every service builds and passes go vet ./..., and accounts/fixtures tests pass. The full suites run in CI.

Not verified here: a composed boot with this exact head; sdk-go#68 proved it with the dependency overridden.

🤖 Generated with Claude Code

…inside a composition

sdk-go v0.3.1 resolved a service's own endpoint from the first workspace
file above the process. A host run from its checkout or from a released
tag in the module cache found its own development workspace, which names
the module differently from the composition, so telemetry and accounts
exited at start. v0.3.2 (codefly-dev/sdk-go#68) trusts a found workspace
only when it is the process's injected composition.

accounts' fixture seeding moves from codefly.Fixture() to
fixture.Selected(), the API sdk-go#65 moved it to.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@antoinetoussaint-byte
antoinetoussaint-byte added this pull request to the merge queue Oct 12, 2026
Merged via the queue into main with commit 9b478dc Oct 12, 2026
24 checks passed
antoinetoussaint-byte added a commit that referenced this pull request Oct 12, 2026
…ext cutover

The four conflicts were the accounts and auth-gateway go.mod/go.sum. Both
intents are kept: main's move to sdk-go v0.3.2 (#1095), and this branch's core
pin (core main's merge commit for core#783) and sdk-go/workcontext v0.1.0. The
require lines were combined by hand and go.sum regenerated with go mod tidy;
minimal version selection keeps core on the pinned commit.

No contract artefact conflicted, and a full pass of the pinned codefly 0.1.185
pipeline (proto, go generate, contracts, SDK) over the merged tree changes
nothing.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@antoinetoussaint-byte
antoinetoussaint-byte deleted the deps/sdk-go-v0.3.2 branch October 25, 2026 17:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant