Epic: split CI per language package — fix and release one package fast, without running every other package's pipeline #354
Labels
No labels
code-review
correctness
dos
performance
security
severity/high
severity/low
severity/medium
tech-debt
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
h-dv/code-index#354
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal (operator, 2026-10-11)
When a language has a problem, we must be able to fix it and release an update of that package only, quickly, without running the CI of every other package or a core release.
What already exists
.provenance).pkg/<id>/v<version>tag publishes a package without a core release, then merges it into the signedpkg-channel.What the first real use showed (de.h-dv.ruby 0.10.0, 2026-10-11)
Getting one package out took five workflow runs (1089, 1090, 1094, 1102, and the core release 1088), about six hours, two operator approvals for dispatches, and a hotfix release (v0.36.1, PR #353). Zammad saw a 404 in between and needed a manual
plugin addworkaround.package_ci_gate.shrequires the package's own package-ci leg, in scope, for the exact tagged commit.tests/packages/<name>leaves that leg out, so the gate pollsabsentuntil its deadline.require_ci_green.shusesDEADLINE_MINUTES=50, but the ruby leg takes 74 min and the others 63–65 min (run 1090). Even a timely dispatch cannot beat it.crates/guest/languages, host plugin files). A fix to one moves several packages and runs all their legs; #348 moved six packages at once.pkg%2F…segment,merge_relocated, and a download check.package_channel_check.sh --downloadable, so the last check failed with a usage error after the channel was already published. The published channel itself is correct.Lanes (proposal; plan to be agreed before work starts)
absent.release_gate.plugin updateon a project. Timed end to end, with no host jobs and no other package's legs. It is the acceptance test for this epic.Acceptance
plugin update <id>installs it on a real project (zammad-dev is the field reference).Related: #309, #318, #344, #345, #353.
🤖 Generated with Claude Code
Plan for the v0.37 train (operator decision, 2026-10-12)
Scope: all of this epic, including lane C for all six languages, plus #355, #356 and the release-note fix (
languages owner ruby package, notenable). Lane A uses the inline leg. One full run, one PR, one CI round, one tag set.Measured before planning (run 1090, ruby leg, 73.9 min)
ruby_guest_rebuild, 12 min;--releasecompile for corpus parity and cost, 30 min.crates/plugins/src/*.rs) is compiled into every package lane. That is why one walker edit moves all packages.--downloadable.Wave 1 (running)
package_leg.sh <name> <tier>used by package-ci and package-release. Tierreleasegrades only the shipped bytes. Corpus and overhead legs run as a parallel job, plus nightly. package-release runs the leg inline with no deadline wait. Scripts come from the workflow's own commit, or the dispatch is refused, graded inrelease_gate. Compile cost is cut and measured.pkg%2F…belong to package-release. A core release takes them from the published channel, never from the in-tree bump. Its channel seed checks that each URL downloads. Release-note text fix.typescript.rs.Wave 2 (after own-c0)
python, csharp, rust, javascript and typescript, one lane each, following own-c0's recipe.
Then
train-037, one full gate run, version bump, PR and CI.plugin update, timed. Any package whose bytes the ownership move changes gets its own package release through the new pipeline, which is the drill run for real.🤖 Generated with Claude Code
v0.37.0 released (release run 1128 green). It ships the per-package extractors for php, python, csharp, rust, javascript and typescript as 0.1.3, plus the catalog rule. de.h-dv.ruby 0.10.1 is withheld from the catalog until its own package release, and the release says so.
Dogfood on the release binary, this repo, 1355 files:
resolved_by..rbxfixtures.Still open in this epic:
pkg/de.h-dv.ruby/v0.10.1). It is not done yet and needs operator approval.Found while dogfooding, being fixed for the next patch release:
languages owner <lang> package) re-extracted the whole tree. It also left the rollback generation holding the wrong files: the carried ones instead of the switched ones.lang=vueandlang=sveltematched nothing.type, imported calls unresolved). Ship the fix as a package release, not a host release #315Independent package-release evidence from Python 0.1.4 (2026-10-22): run 1476 completed its four normal stages in 15m20s: own-package qualification, pack/sign/operator install and negative controls, immutable publication, signed-channel merge and published read-back. No host CI job or other language package leg ran in that release workflow, and no core release was needed.
Independent operator proof used the published core
0.41.8 (4734318a)with its original signed Python 0.1.3 bundle in an isolated project. The reported Hatch wheel layout initially returnedabi.frame_truncated.plugin update de.h-dv.python --grant requested --yes, using the default signed package channel and no custom trust, selected official Python 0.1.4. Re-indexing produced an active-generation layout ofready,withheld=0, no reason. The separately downloaded official artifact also mapped the expected modules and excluded files outside the wheel package.This does not establish the whole package-only PR acceptance: PR #407 combines host diagnostics with a Python layout helper change under
guest-kit, so its PR qualification correctly selected all packages. That shared-input fan-out remains a distinct optimization/ownership question. This evidence establishes the independent release and operator-update path, not completion of every acceptance item.Closing after auditing the previously missing F drill against work already shipped, rather than reimplementing the old plan.
Real package-only fix: PR #489 (Svelte0.2.4), head
fd19c6e500, merged asf349d01bdf. Its changed files are the Svelte guest, package bytes/fixtures/catalog row and package-owned tests; no runtime or core-version edit. The classifier explicitly reported mode=packages, packages=svelte and every host group false. Linux run2182 skipped host qualification jobs; Windows run2181 skipped its native build/test job; pilot run2184 skipped both unrelated pilots. Other package matrix entries were scope no-ops. The Svelte PR qualification run2183 completed in4m55s.The independent package-tag release run2189 completed all four stages in4m18s: own-byte qualification, pack/sign/operator checks, immutable publication and signed-channel update. No hand dispatch or core release was needed. Published assets: https://git.h-dv.de/h-dv/code-index/releases/tag/pkg%2Fde.h-dv.svelte%2Fv0.2.4 . Earlier comments already reconciled lanesA–E and left only this end-to-end evidence outstanding.
Fresh operator verification today used unchanged published core0.41.43 in a new isolated real project/store. Installed official signed Svelte0.2.3, indexed a keyed each block, then ran
plugin update de.h-dv.svelte --grant requested --yesagainst the default signed channel. Before: wrapper1, missing body read0, parse errors0. After official0.2.4: wrapper1, body read1, parse errors0. Core binary/version unchanged throughout. The store contained only the old package before update. Complete fresh-store drill1.206s; named update0.587s. Raw command outputs and receipt: /tmp/cosi-044-svelte-drill-timed/commands.json and verification.json.This establishes the bounded package-only PR→release/channel→operator-update path. General host/package isolation refinements remain independently tracked in #318; broader startup and resolver gaps remain separate.