The post-merge conformance job on main has failed identically on both runs since #46 (jsr-test-consumption) landed — observed while landing #47 (deltic 0.2.0), whose required PR checks were green and whose failure is byte-identical to the pre-existing one, so this is not deltic-related:
Install the component-test tools at the pinned revision
Error: conformance/driver-ct/deltic/package-lock.json: no rev pin found for @polymorph/component-test-js
Evidence: run 32065273396 (#46 merge) and run 32381812648 (#47 merge) fail in the same step with the same message.
Looks like the shared component-test setup action still derives its tool pin from a git rev entry for @polymorph/component-test-js in conformance/driver-ct/deltic/package-lock.json, which the JSR consumption migration removed/changed. Either the action's pin source needs re-pointing at the JSR-era pin location, or the workflow's uses: ref/inputs need the post-#46 shape.
(Filed during the family-wide deltic 0.2.0 upgrade; the deltic legs themselves are green locally — run-deltic 5/2 n/a, delegated 6/1 n/a, browser twins identical.)
The post-merge
conformancejob on main has failed identically on both runs since #46 (jsr-test-consumption) landed — observed while landing #47 (deltic 0.2.0), whose required PR checks were green and whose failure is byte-identical to the pre-existing one, so this is not deltic-related:Evidence: run 32065273396 (#46 merge) and run 32381812648 (#47 merge) fail in the same step with the same message.
Looks like the shared component-test setup action still derives its tool pin from a git rev entry for
@polymorph/component-test-jsinconformance/driver-ct/deltic/package-lock.json, which the JSR consumption migration removed/changed. Either the action's pin source needs re-pointing at the JSR-era pin location, or the workflow'suses:ref/inputs need the post-#46 shape.(Filed during the family-wide deltic 0.2.0 upgrade; the deltic legs themselves are green locally — run-deltic 5/2 n/a, delegated 6/1 n/a, browser twins identical.)