Remove the jco conformance legs; the deltic rows carry both postures - #40
Merged
Conversation
jco support/coverage is retiring family-wide, retained only in polymorph-webcrypto (operator ruling recorded on lann/deltic#14). The deltic rows cover both former postures — stock Deno (deltic-deno*) and headless Chromium (deltic-browser*, #39) — so the four jco targets come out: conformance/driver-ct/jco/, their targets.toml blocks, the justfile recipes and aggregate/pins wiring, the CI Node step and jco js-lock, and the .gitignore entries. matrix.md regenerated for the surviving seven targets (42 results, 0 failing). Also, while touching those lines: the CI publish action's results list gains the deltic-browser rows it missed in #39 (the local aggregate recipe already passed them — the same completion #38 made for the deno rows), and conformance/README's targets table gains the same rows. Gates: gha::rust-checks, gha::smoke, CONFORMANCE_BROWSER=1 gha::conformance-checks (7 targets / 42 results / 0 failing), gha::interop — all green locally. The post-gate touch-up was the CI-yaml results list only (not locally executable).
lann
enabled auto-merge
August 10, 2026 19:03
This was referenced Aug 10, 2026
lann
added a commit
that referenced
this pull request
Aug 10, 2026
…ostures" This reverts commit 677daac (PR #40, reverse of 8b16928): the jco legs return until the perf comparison against the deltic legs has been run (operator call, 2026-08-10 — lann/deltic#17 is the tracking issue; the family ruling that jco support ultimately remains only in polymorph-webcrypto stands, lann/deltic#14). The two #39 wiring completions that rode PR #40 (the publish action's deltic-browser results rows, conformance/README's deltic-browser table rows) are re-applied in the follow-up commit rather than lost with the revert.
lann
added a commit
that referenced
this pull request
Aug 10, 2026
The publish action's results list keeps the deltic-browser rows and the setup action's js-locks gains deltic's lockfile (both missing since #39 — the local justfile wiring already had them), and conformance/README's targets table keeps its deltic-browser rows. Content-identical to what PR #40 carried alongside the removal.
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.
jco support/coverage is retiring family-wide — retained only in polymorph-webcrypto (operator ruling recorded on lann/deltic#14). The deltic rows cover both former jco postures — stock Deno (
deltic-deno*) and headless Chromium (deltic-browser*, #39) — so the four jco targets come out:conformance/driver-ct/jco/(runner, transpile-stamp machinery, package tree)targets.tomlblocks; the justfile recipes and aggregate/pins wiring; the CI Node step and jco js-lock; the.gitignoreentriesmatrix.mdregenerated for the surviving 7 targets (42 results, 0 failing) viaconformance-ct::matrix-updateAlso, while touching those lines: the CI publish action's
results:list gains the deltic-browser rows it missed in #39 (the local aggregate recipe already passed them — the same completion #38 made for the deno rows), and conformance/README's targets table gains the same rows.Gates (local):
gha::rust-checks,gha::smoke,CONFORMANCE_BROWSER=1 gha::conformance-checks(7/42/0),gha::interop— all green.