Skip to content

chore: upgrade picomatch to ^4.0.4 to address CVE-2026-33671, CVE-202… #472

chore: upgrade picomatch to ^4.0.4 to address CVE-2026-33671, CVE-202…

chore: upgrade picomatch to ^4.0.4 to address CVE-2026-33671, CVE-202… #472

Triggered via push June 8, 2026 23:38
Status Success
Total duration 14m 46s
Artifacts 4

release-dev.yml

on: push
Matrix: build / build
publish-to-registry  /  merge
21s
publish-to-registry / merge
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
build / build (linux/amd64)
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/upload-artifact@v4, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
build / build (linux/arm64)
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/upload-artifact@v4, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
publish-to-registry / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/

Artifacts

Produced during runtime
Name Size Digest
digests-linux-amd64 Expired
244 Bytes
sha256:a4a531a88c77eb147699d076b61129f47887f6e6df86302f4ae291abc3a7abc4
digests-linux-arm64 Expired
244 Bytes
sha256:26c5840bdd9a6484fea425d8522236b038d7f9a3e1b21579a61d03ac27573742
sourcebot-dev~sourcebot~74SZIW.dockerbuild
173 KB
sha256:71d67025962492054e318ea12a032f114242c9cdcca1c763c81c80f0a4ee60be
sourcebot-dev~sourcebot~U075ED.dockerbuild
176 KB
sha256:bdc48a7ae16372d4217529c394b24f60977b6d68e95196baf8422da7e5e0fefa