You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Move this repository to codefly-dev/core v0.19.1, the current core release, and release it, so that everything built on it can move too.
Where it stands
Both modules (root and workcontext/) pin core v0.15.0 (README says v0.13.0). Almost every Go repo in the fleet depends on sdk-go, so this goes first.
v0.19.0 and v0.19.1 change no CLI-agent contract (protocol 1, startup protocol 2). The work is the jump from the current pin, through every core release between, and the breaking changes those releases made: the exposure declaration (v0.14), Inspect renamed to Decode (v0.15), Work Context moving to sdk-go/workcontext / core workcontext, and the Go 1.27.x toolchain.
Done when
Every go.mod in the repo requires core v0.19.1. Use released tags only: no pseudo-versions, no replace.
Build, vet, the race suite and the repo's own gates pass locally and in CI.
From saas-sdk-go#38: saas-sdk-go needs nothing from this issue. workcontext/v0.1.0 (1ce8b27) already builds and vets in saas-sdk-go's graph with core v0.19.1, so your workcontext release will be a plain pin bump there. saas-sdk-go is blocked on the host instead: module-saas-starter#1093 has to merge and be released before its conformance job can build. Details: codefly-dev/saas-sdk-go#38 (comment)
solution-runtime-go#62 needs no sdk-go or workcontext change: codefly-dev/solution-runtime-go#64 builds on core v0.19.1 with the released sdk-go v0.3.2 and workcontext/v0.1.0 as they are. Gate green locally. One consequence of v0.3.1+ worth knowing for other consumers: the runtime never called codefly.Init, so endpoint resolution returned nothing until it did — the PR now calls it at boot and refuses an unset CODEFLY__MODULE. When #70 releases, solution-runtime-go moves by a pin bump; nothing there waits on it.
lazybox has finished working on this.codex (Astra · high) held it from 2026-10-13 19:47 UTC until 2026-10-15 05:45 UTC. The working label has been removed; this comment is the record.
Activity
antoinetoussaint-byte commentedon Oct 12, 2026
From saas-sdk-go#38: saas-sdk-go needs nothing from this issue.
workcontext/v0.1.0(1ce8b27) already builds and vets in saas-sdk-go's graph with core v0.19.1, so your workcontext release will be a plain pin bump there. saas-sdk-go is blocked on the host instead: module-saas-starter#1093 has to merge and be released before its conformance job can build. Details: codefly-dev/saas-sdk-go#38 (comment)antoinetoussaint-byte commentedon Oct 12, 2026
solution-runtime-go#62 needs no sdk-go or
workcontextchange: codefly-dev/solution-runtime-go#64 builds on core v0.19.1 with the released sdk-go v0.3.2 andworkcontext/v0.1.0as they are. Gate green locally. One consequence of v0.3.1+ worth knowing for other consumers: the runtime never calledcodefly.Init, so endpoint resolution returned nothing until it did — the PR now calls it at boot and refuses an unsetCODEFLY__MODULE. When #70 releases, solution-runtime-go moves by a pin bump; nothing there waits on it.antoinetoussaint-byte commentedon Oct 13, 2026
lazybox has finished working on this.
codex(Astra · high) held it from 2026-10-13 19:47 UTC until 2026-10-15 05:45 UTC. Theworkinglabel has been removed; this comment is the record.claim detail