Skip to content

codegen-orchestrator-1708: Pin published kit 0.11.0 and its generated artifacts - #848

Merged
vladmesh merged 4 commits into
mainfrom
pipeline/codegen-orchestrator-1708
Oct 19, 2026
Merged

vladmesh merged 4 commits into
mainfrom
pipeline/codegen-orchestrator-1708

Conversation

@vladmesh

Copy link
Copy Markdown
Owner

What

Candidate HEAD c6bfead, tree a3a19c3d74713fe5223fcab3187241cf8fd277ab, branch pipeline/codegen-orchestrator-1708 on base main f987901. Workspace clean (git status --porcelain empty). TASK.md not committed.

Why

Pin the orchestrator's new-product scaffolding to published kit core0.11.0 and align installed tooling, activated catalog provenance and the genuine CI-produced rendered fixture/locks with its exact released commit. This is the final source increment of sprint1496 d4, in codegen_orchestrator only. Existing products are not bulk-upgraded or deployed.

How verified

CI runs Backend Docker-in-Docker Integration Tests, Build Service Image Candidates, Build Worker Base Image Candidates, CI Contract, Detect Changed Services, Fast Checks (Unit Tests), Lint (Ruff), Publish Service Image Release, Publish Worker Base Images, Required CI Gate, Service Image Entrypoint Imports on c6bfeadb9757; the merge waits for them to pass.

Card: codegen-orchestrator-1708

…ommit 59a0752c

The seed pins the annotated release tag 0.11.0; the root and LangGraph tooling
manifests, the activated catalog commit/tooling host and the capability manifest
provenance (v27, rendered) name its peeled commit. Catalog bytes, semantic digest
and core 2.6.0 are unchanged between 14fa729c and 59a0752c.
…kit guide

The pin is now a release tag, so the witness and mechanical-install fixtures
take SHA-valued catalog/tooling fields from the activated snapshot and hand the
probe the template ref; the single-source test ties the render's tooling, the
installed tooling and the activation to one commit, and the upgrade integration
test reuses the shared recorded-commit matcher. The kit guide and changelog
describe the 0.11.0 boundary.
…ed deploy workflows

The render, its provenance and both locks are the bytes of the push-triggered
Released template fixture run 39186762156 for candidate 07643c2 (render job
117850710818, artifact 12158231775; locks job 117850711064, artifact
12158815757), committed unchanged. The IPv6 deploy recognizer admits the
reviewed SSH-action workflow that existing products keep until a Copier update
and the native ssh workflow of 0.11.0; the old shape is proven against its
byte-preserved render with producer hash provenance.
…grade test

The runner proof expected the scheduler's published template ref and the scaffold's
requested ref to equal the kit commit; with a tag seed they equal the seed's ref, read
through load_template_pin, and template_evidence still resolves the recorded ref to the
kit commit. The released-upgrade test runs in an image without the shared package, so
it no longer imports it: it keeps its dependency-free recorded-ref check and requires
the rendered tooling commit to be the one the pinned release tag peels to at its source.
@vladmesh
vladmesh merged commit 28831f1 into main Oct 19, 2026
28 checks passed
@vladmesh
vladmesh deleted the pipeline/codegen-orchestrator-1708 branch October 19, 2026 02:39
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