Skip to content

remove redundant install #7

remove redundant install

remove redundant install #7

Triggered via push April 3, 2026 00:58
Status Failure
Total duration 51s
Artifacts

ci.yml

on: push
Matrix: ci
Fit to window
Zoom out
Zoom in

Annotations

17 errors and 3 warnings
CI (windows-latest)
Process completed with exit code 1.
CI (ubuntu-latest)
The strategy configuration was canceled because "ci.windows-latest" failed
CI (ubuntu-latest)
Process completed with exit code 1.
CHK-03 -- stale src / triggers build.client rebuild when manifest is stale, exit 0: tests/integration/golden/check-client.spec.ts#L75
expected ' ............\n :::: :-------…' to include 'build-client'
CHK-02 -- up-to-date manifest / silent success when manifest is newer than src, exit 0: tests/integration/golden/check-client.spec.ts#L52
stdout should be empty/whitespace but got: "............ :::: :--------:. :::: .:-------:. ::::: .:------. :::::: .:-----. :::::: :-----: :::::: .:----. ::::::: .----. ::::::::.. ---: .:::::::::. :-: ..:::::::::::: ...:::: check-client command (stub)": expected false to be true - Expected - 1 + Received + 1 - true + false
CHK-01 -- no dist directory / triggers build.client when no dist exists, exit 0: tests/integration/golden/check-client.spec.ts#L28
expected ' ............\n :::: :-------…' to include 'build-client'
Scaffold / tsdown.config.ts exists: tests/unit/scaffold.spec.ts#L32
expected false to be true - Expected - 1 + Received + 1 - true + false
Scaffold / package.json has engines >=20.19.0: tests/unit/scaffold.spec.ts#L11
expected '>=24.0.0' to include '20.19.0'
CI (macos-latest)
The strategy configuration was canceled because "ci.windows-latest" failed
CI (macos-latest)
The operation was canceled.
CHK-03 -- stale src / triggers build.client rebuild when manifest is stale, exit 0: tests/integration/golden/check-client.spec.ts#L75
expected ' ............\n :::: :-------…' to include 'build-client'
CHK-02 -- up-to-date manifest / silent success when manifest is newer than src, exit 0: tests/integration/golden/check-client.spec.ts#L52
stdout should be empty/whitespace but got: "............ :::: :--------:. :::: .:-------:. ::::: .:------. :::::: .:-----. :::::: :-----: :::::: .:----. ::::::: .----. ::::::::.. ---: .:::::::::. :-: ..:::::::::::: ...:::: check-client command (stub)": expected false to be true - Expected - 1 + Received + 1 - true + false
CHK-01 -- no dist directory / triggers build.client when no dist exists, exit 0: tests/integration/golden/check-client.spec.ts#L28
expected ' ............\n :::: :-------…' to include 'build-client'
Scaffold / tsdown.config.ts exists: tests/unit/scaffold.spec.ts#L32
expected false to be true - Expected - 1 + Received + 1 - true + false
Scaffold / package.json has engines >=20.19.0: tests/unit/scaffold.spec.ts#L11
expected '>=24.0.0' to include '20.19.0'
CI (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CI (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
CI (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/