Skip to content

chore: Cherry-picked changes from upstream #696

chore: Cherry-picked changes from upstream

chore: Cherry-picked changes from upstream #696

Triggered via pull request April 20, 2026 16:39
Status Success
Total duration 2m 56s
Artifacts

target-dir.yml

on: pull_request
Matrix: target-dir
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
Test custom target-dir on ubuntu-latest
Error [ERR_STREAM_WRITE_AFTER_END]: write after end at _write (node:internal/streams/writable:487:11) at Writable.write (node:internal/streams/writable:508:10) at ReadStream.ondata (node:internal/streams/readable:1012:24) at ReadStream.emit (node:events:508:28) at addChunk (node:internal/streams/readable:563:12) at readableAddChunkPushByteMode (node:internal/streams/readable:514:3) at Readable.push (node:internal/streams/readable:394:5) at node:internal/fs/streams:293:14 at FSReqCallback.wrapper [as oncomplete] (node:fs:669:5)
Test custom target-dir on macos-latest
Error [ERR_STREAM_WRITE_AFTER_END]: write after end at _write (node:internal/streams/writable:487:11) at Writable.write (node:internal/streams/writable:508:10) at ReadStream.ondata (node:internal/streams/readable:1012:24) at ReadStream.emit (node:events:508:28) at addChunk (node:internal/streams/readable:563:12) at readableAddChunkPushByteMode (node:internal/streams/readable:514:3) at Readable.push (node:internal/streams/readable:394:5) at node:internal/fs/streams:293:14 at FSReqCallback.wrapper [as oncomplete] (node:fs:669:5)
Test custom target-dir on windows-latest
Error [ERR_STREAM_WRITE_AFTER_END]: write after end at _write (node:internal/streams/writable:487:11) at Writable.write (node:internal/streams/writable:508:10) at ReadStream.ondata (node:internal/streams/readable:1012:24) at ReadStream.emit (node:events:508:28) at addChunk (node:internal/streams/readable:563:12) at readableAddChunkPushByteMode (node:internal/streams/readable:514:3) at Readable.push (node:internal/streams/readable:394:5) at node:internal/fs/streams:293:14 at FSReqCallback.wrapper [as oncomplete] (node:fs:669:5)
Test custom target-dir on ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@17d0e2bd7d51742c71671bd19fa12bdc9d40a3d6. 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/
Test custom target-dir on macos-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@17d0e2bd7d51742c71671bd19fa12bdc9d40a3d6. 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/
Test custom target-dir on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@17d0e2bd7d51742c71671bd19fa12bdc9d40a3d6. 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/