Skip to content

chore: update progress for US-083 #13

chore: update progress for US-083

chore: update progress for US-083 #13

Triggered via push March 18, 2026 08:07
Status Failure
Total duration 33s
Artifacts

pkg-pr-new.yaml

on: push
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
publish
Cannot find module '@secure-exec/browser' or its corresponding type declarations.
publish
Cannot find module '@secure-exec/browser' or its corresponding type declarations.
publish
Cannot find module '@secure-exec/core' or its corresponding type declarations.
publish
Cannot find module '@secure-exec/core' or its corresponding type declarations.
publish
Cannot find module '@secure-exec/browser' or its corresponding type declarations.
publish
Cannot find module '@secure-exec/browser' or its corresponding type declarations.
publish
Cannot find module '@secure-exec/core' or its corresponding type declarations.
publish
Cannot find module '@secure-exec/core' or its corresponding type declarations.
publish
Cannot find module '@secure-exec/core' or its corresponding type declarations.
publish
Cannot find module '@secure-exec/node/internal/bridge-loader' or its corresponding type declarations.
publish
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/