Skip to content
ci

build(deps): bump actions/create-github-app-token from 2 to 3 #2836

Sign in to view logs

build(deps): bump actions/create-github-app-token from 2 to 3

build(deps): bump actions/create-github-app-token from 2 to 3 #2836

Triggered via pull request March 16, 2026 04:42
@dependabotdependabot[bot]
opened #493
dependabot/github_actions/actions/create-github-app-token-3
Status Success
Total duration 49s
Artifacts 6

ci.yml

on: pull_request
multi
16s
multi
error
24s
error
debug
21s
debug
docker-driver
7s
docker-driver
endpoint
46s
endpoint
buildkitd-config
17s
buildkitd-config
buildkitd-config-inline
15s
buildkitd-config-inline
standalone-cmd
12s
standalone-cmd
standalone-action
20s
standalone-action
append
15s
append
platforms
19s
platforms
docker-context
8s
docker-context
windows-error
22s
windows-error
keep-state
14s
keep-state
keep-state-error
7s
keep-state-error
Matrix: build-ref
Matrix: cache-binary
Matrix: cleanup
Matrix: driver
Matrix: k3s
Matrix: main
Matrix: use
Matrix: with-qemu
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 5 warnings
keep-state-error
Cannot use keep-state with docker driver
windows-error
ERROR: no matching manifest for windows(10.0.26100)/amd64 in the manifest list entries
error
ERROR: failed to initialize builder builder-ca9493db-67eb-41f3-a124-4dc01829d42f (builder-ca9493db-67eb-41f3-a124-4dc01829d42f0): Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
build-ref (refs/tags/v0.5.1)
Attestations are only supported by buildx >= 0.10.0; the inputs 'attests', 'provenance' and 'sbom' are ignored.
error
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. 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/
k3s (v0.10.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. 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/
k3s (v0.11.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. 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/
k3s (latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. 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/

Artifacts

Produced during runtime
Name Size Digest
docker~setup-buildx-action~2GRWT8.dockerbuild
18.5 KB
sha256:17d5a0f94b1af00d910929bdd489626a102aa63679dff340e8e2fbb3da301eba
docker~setup-buildx-action~B8BXPH.dockerbuild
16.6 KB
sha256:33d431dd633401a96ef0a06620e8a8e7f6673948f47c36641153fb7eb428daa9
docker~setup-buildx-action~NXIIR6.dockerbuild
43.7 KB
sha256:6aa3a4e404cb03ad8b07e2bfe3950c5e76b540626a2b6f19b7faf746fe36f27f
docker~setup-buildx-action~ULMCK9.dockerbuild
17.1 KB
sha256:4cb093c2918f69f3e644762c9c4af17dffa84e8290848a436b852f3c421285af
docker~setup-buildx-action~W1YQMO.dockerbuild
18.4 KB
sha256:a17c9223b066fed9b3577ec6b3db3a165e224f7518ef90c7a0286ae5b6fd4691
docker~setup-buildx-action~Z0OB1I.dockerbuild
13.2 KB
sha256:00a989629060e84978c30d6e5cfa39da76fe8545ea99cb56af8da37f561358e0