Skip to content

docs(clone): stronger usage example (mutation + lodash divergence) + … #22

docs(clone): stronger usage example (mutation + lodash divergence) + …

docs(clone): stronger usage example (mutation + lodash divergence) + … #22

Triggered via push May 15, 2026 10:43
Status Success
Total duration 28s
Artifacts 1

ci.yml

on: push
ci  /  preflight
ci / preflight
ci  /  publish
24s
ci / publish
ci  /  ...  /  gitleaks
7s
ci / security / gitleaks
ci  /  ...  /  dependency-review
ci / security / dependency-review
ci  /  ...  /  osv-scanner
15s
ci / security / osv-scanner
Fit to window
Zoom out
Zoom in

Annotations

3 warnings and 2 notices
ci / security / gitleaks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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 / security / osv-scanner
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5. 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 / publish
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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 / security / gitleaks
gitleaks: no leaks found
ci / publish
Moved rolling tag v1 to 3a7cc07f236bc76b1810815d2f9fa8790be1b2a6

Artifacts

Produced during runtime
Name Size Digest
gitleaks-report Expired
6.97 KB
sha256:1272ce37ecd8392eaf84637550fa5f30a20cebbe129b2285a626bcc9dc4c94d2