Adopt released Core v0.19.8: authenticated-v2 process groups, verified release publication, stamped generated clients, and runnable-bindings --check on a fresh checkout by antoinetoussaint-byte · Pull Request #1209 · codefly-dev/cli

fix(generate): runnable-bindings materializes pinned modules, so --check can run on a fresh checkout

antoinetoussaint-byte

and

claude

committed

1fac1a7

fix(release): verify artifacts and carry generated client versions

antoinetoussaint-byte

committed

91ff434

fix(stop): retain incompatible live process identity evidence

antoinetoussaint-byte

committed

cefe537

Merge remote-tracking branch 'origin/main' into stale-generated-output/runnable-bindings-check-materializes

antoinetoussaint-byte

committed

fdaf95e

fix(generators): stamp the Python project version by TOML ownership

antoinetoussaint-byte

committed

ddd27e6

fix(stop): preserve registry refusals through cleanup fallbacks

antoinetoussaint-byte

committed

293c291

fix(stop): consume authenticated workspace provenance from Core

antoinetoussaint-byte

committed

9796619

fix(stop): report each preserved group once across recovery passes

antoinetoussaint-byte

committed

8add946

Merge container attribution fix and adopt released Core v0.19.8

antoinetoussaint-byte

committed

e9cf1cf

docs(generate): a failed preparation preserves the existing binding; runnable-bindings materializes pinned modules

antoinetoussaint-byte

and

claude

committed

31387a5

Navigation Menu

Repository navigation

Adopt released Core v0.19.8: authenticated-v2 process groups, verified release publication, stamped generated clients, and runnable-bindings --check on a fresh checkout - #1209

Adopt released Core v0.19.8: authenticated-v2 process groups, verified release publication, stamped generated clients, and runnable-bindings --check on a fresh checkout#1209
antoinetoussaint-byte merged 10 commits into
mainfrom
stale-generated-output/runnable-bindings-check-materializes

Commits on Oct 27, 2026

fix(generate): runnable-bindings materializes pinned modules, so --check can run on a fresh checkout

fix(release): verify artifacts and carry generated client versions

fix(stop): retain incompatible live process identity evidence

Merge remote-tracking branch 'origin/main' into stale-generated-output/runnable-bindings-check-materializes

fix(generators): stamp the Python project version by TOML ownership

fix(stop): preserve registry refusals through cleanup fallbacks

fix(stop): consume authenticated workspace provenance from Core

fix(stop): report each preserved group once across recovery passes

Merge container attribution fix and adopt released Core v0.19.8

docs(generate): a failed preparation preserves the existing binding; runnable-bindings materializes pinned modules