Skip to content

fix: remove hardcoded local path from DTCG conformance test #155

fix: remove hardcoded local path from DTCG conformance test

fix: remove hardcoded local path from DTCG conformance test #155

Triggered via push June 15, 2026 19:16
Status Failure
Total duration 55s
Artifacts

test.yml

on: push
test
35s
test
npm-registry-smoke-windows
28s
npm-registry-smoke-windows
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
test
Process completed with exit code 1.
test
@google/design.md#test: command (/home/runner/work/design.md/design.md/packages/cli) /home/runner/.bun/bin/bun run test exited (1)
error: expect(received).toBe(expected): packages/cli/src/linter/dtcg/conformance.test.ts#L107
Expected: 0 Received: 1 at <anonymous> (/home/runner/work/design.md/design.md/packages/cli/src/linter/dtcg/conformance.test.ts:107:27)
npm-registry-smoke-windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/