Repository navigation
deploy.yml is red on main: the pinned charly predates the repo's schema version #10
Description
The defect
main's deploy.yml (candy workflow) fails on every push, including on main itself
(latest: run 36238774995). The failing step is charly box validate:
charly: error: config schema 2026.261.1747 is newer than this charly supports (max 2026.249.2125).
Update charly (reinstall the latest opencharly package, or run 'task build:binary' from a fresh checkout and use ./bin/charly)
Root cause
The load-time schema gate (sdk/loaderkit/load_unified.go GateSchemaVersion) requires the
pinned charly's HEAD schema to exactly equal the config's version:. deploy.yml pins
v2026.258.0219, whose HEAD schema is 2026.249.2125, while charly.yml is stamped
2026.261.1747 — so the pin is older than the schema it is asked to validate. The gate
fails closed.
The fix
Bump the deploy.yml pin to a charly release whose HEAD schema IS 2026.261.1747 — e.g.
v2026.269.1034 (charly/go.mod pins spec v0.2026269.759, whose SchemaVersion is
2026.261.1747). Verified: a charly built from v2026.269.1034 validates this manifest
clean (charly box validate: OK … 0 warnings, 0 errors).
Surfaced while landing the Cua integration (opencharly/plugin-cua#2, opencharly/layer-cua#2);
not a blocker for those PRs, but main here is red until it is fixed.
Activity
aitrawog commentedon Sep 27, 2026
Progress — you are unblocked by the chain, not by anything in this repo
The pinned-
charlystaleness this issue reports is the last leg of the schema-versioning-removal / R5 cutover. Status:Landed:
spec v0.2026270.938,sdk v0.2026270.1147,plugin-service v2026.270.1351,plugin-package v2026.270.1351,plugin-build v2026.270.1414,plugin-migrate v2026.270.1359,plugin-fleet#24.Still gating the
charlyleg:plugin-box#16,plugin-enc#4,plugin-deploy-pod#14,plugin-deploy-local#7,plugin-deploy-vm#27— until they merge,charlypanics (plugin ships NO CUE schema … no schema-less plugin).charly/charly/version.go:78still calls the removedcalver.LatestSchemaCalVer(delete it).disposable: truebed → corpus wave → a newcharlytag.Once that tag lands, re-pin this repo's
charlyand this issue is moot. I will comment here with the tag when it lands.Assisted-by: OpenCode ollama-cloud/deepseek-v4.1-flash (analysed on a live system)
aitrawog commentedon Sep 28, 2026
STATUS — still gated by the
charlyhost leg (nothing to do in this repo yet)The schema wave is complete;
charly#716is functionally green and is clearing its last block (the cross-repo skew, worked viacharly#717). Whencharly#716merges and tags, re-pin this repo'scharlyand this issue becomes moot. I will comment here with the new tag the moment it lands.Assisted-by: OpenCode ollama-cloud/deepseek-v4.1-flash (analysed on a live system)
Agent:
coordination· sessionses_f26225bfffferfo4tnJQw1ePqMaitrawog commentedon Oct 6, 2026
RESOLVED — superseded; the workflow this issue names no longer exists.
opencharly/plugin-jetkvmorigin/mainno longer shipsdeploy.yml; its workflows areci.yml(Go gates, last main run green: 2026-09-29) andtag-on-merge.yml, and the reponow declares a root
charly.ymlwithdiscover:so its candy is actually scanned. Thestale pin the issue reported is gone with the workflow. Reopen if a future
charly box validateon main fails on a schema-version mismatch.Agent: issue-triage · session 01a11139-cee6-76a9-a880-9b07eb6f1cab
Assisted-by: pi ollama-cloud/deepseek-v4.1-flash (analysed on a live system)