chore(deploy): roll platform onto python-runtime v0.4.1 - #477
Merged
Conversation
Roll the platform onto the v0.4.1 continuo-python-runtime-<engine> image (adapters renamed to continuo-<engine>-adapter; runtime + adapter installed from PyPI instead of built from source). Bumps every reference: chart default (validation.imageTag), docker-compose, Makefile, scripts/setup.sh, the tests/e2e provisioning + py-probe fixture, and the executor-controller k8s fixture tests. Image name, entrypoint, run/validation-op commands, uid 65532, and adapter discovery are unchanged, so it is a drop-in. CHANGELOG entry (PATCH). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Simone Carolini <simonecarolini.sc@gmail.com>
Reconcile the arch pack with the v0.4.1 image: it no longer bakes the engine adapter and contract from the continuo-python-runtime workspace at build time — it installs the pinned published packages (continuo-<engine>-adapter, continuo-python-runtime, continuo-engine-contract) from PyPI. Image name, entrypoint, uid, and adapter discovery are unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Simone Carolini <simonecarolini.sc@gmail.com>
_helpers.tpl's CONTINUO_VALIDATION_DEFAULT_TAG (the fallback when validation.imageTag is unset) still pointed at v0.4.0, drifting from the values.yaml default; check-validation-image-pin.sh caught it. The remaining v0.4.0 mentions in the helper are the python-csv feature floor and stay. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Simone Carolini <simonecarolini.sc@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Rolls the Continuo platform onto the v0.4.1
continuo-python-runtime-<engine>image (the release from carolsimone/continuo-python-runtime#50 + #51): adapters renamed tocontinuo-<engine>-adapter, and runtime + adapter + contract now installed from PyPI (versioned) instead of built from source.Bumps every
v0.4.0→v0.4.1reference:validation.imageTag(values.yaml) + CHANGELOG entry (PATCH)docker-compose.yml,Makefile,scripts/setup.shtests/e2e/provisioning + py-probe fixture + executor-controller deploymentexecutor-controller/adapters/k8sfixture tests (kept consistent)docs/arch/reconciled (image installs from PyPI, no longer bakes from workspace)Why it's a drop-in
The platform contract with the image is unchanged: image name (
continuo-python-runtime-<engine>), uid 65532, entrypoint (continuo-runtime) +run/validation-opcommands, and adapter discovery via thecontinuo_engine.adaptersentry-point group. The rename and from-PyPI install are internal to the image.Verified locally
go test ./executor-controller/adapters/k8s/...— passbash scripts/install-test/lint.sh— helm lint + template + kube-linter green across all 4 topologiesThe real gate
CI runs the full e2e on this PR, and the provisioning now pulls v0.4.1 — so each validation job runs the v0.4.1 image as validation-op + node runtime, exactly as executor-controller does in prod. Green e2e = validated drop-in.
Follow-up
This bump ships to installs on the next platform
vX.Y.Zchart release (rides it as a PATCH).🤖 Generated with Claude Code