Fix artifact upload and reduce Claude permission denials in CVE triage #321
dpark01docker.yml
on: push
get-version
6s
paths-filter
4s
Matrix: scan-containers
Matrix: deploy-to-quay
Annotations
5 errors, 20 warnings, and 6 notices
|
scan-containers (core)
ref 'refs/heads/dp/fix-cve-triage-artifact-perms' not found in this repository - https://docs.github.com/rest
|
|
scan-containers (assemble)
ref 'refs/heads/dp/fix-cve-triage-artifact-perms' not found in this repository - https://docs.github.com/rest
|
|
scan-containers (classify)
ref 'refs/heads/dp/fix-cve-triage-artifact-perms' not found in this repository - https://docs.github.com/rest
|
|
scan-containers (mega)
ref 'refs/heads/dp/fix-cve-triage-artifact-perms' not found in this repository - https://docs.github.com/rest
|
|
scan-containers (phylo)
ref 'refs/heads/dp/fix-cve-triage-artifact-perms' not found in this repository - https://docs.github.com/rest
|
|
paths-filter
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@v3. 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/
|
|
build-baseimage-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
|
|
build-baseimage-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
|
|
build-core-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
|
|
build-core-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
|
|
build-phylo-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
|
|
build-assemble-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
|
|
Variables should be defined before their use:
docker/Dockerfile.assemble#L23
UndefinedVar: Usage of undefined variable '$PERL5LIB'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
build-classify-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
|
|
build-classify-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
|
|
build-mega-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
|
|
build-phylo-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
|
|
build-assemble-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
|
|
Variables should be defined before their use:
docker/Dockerfile.assemble#L23
UndefinedVar: Usage of undefined variable '$PERL5LIB'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
build-mega-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6. 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/
|
|
scan-containers (core)
ref 'refs/heads/dp/fix-cve-triage-artifact-perms' not found in this repository - https://docs.github.com/rest
|
|
scan-containers (assemble)
ref 'refs/heads/dp/fix-cve-triage-artifact-perms' not found in this repository - https://docs.github.com/rest
|
|
scan-containers (classify)
ref 'refs/heads/dp/fix-cve-triage-artifact-perms' not found in this repository - https://docs.github.com/rest
|
|
scan-containers (mega)
ref 'refs/heads/dp/fix-cve-triage-artifact-perms' not found in this repository - https://docs.github.com/rest
|
|
scan-containers (phylo)
ref 'refs/heads/dp/fix-cve-triage-artifact-perms' not found in this repository - https://docs.github.com/rest
|
|
scan-containers (baseimage)
Trivy found 0 findings for baseimage (after policy filtering)
|
|
scan-containers (core)
Trivy found 0 findings for core (after policy filtering)
|
|
scan-containers (assemble)
Trivy found 0 findings for assemble (after policy filtering)
|
|
scan-containers (classify)
Trivy found 0 findings for classify (after policy filtering)
|
|
scan-containers (mega)
Trivy found 0 findings for mega (after policy filtering)
|
|
scan-containers (phylo)
Trivy found 0 findings for phylo (after policy filtering)
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
broadinstitute~viral-ngs~B5CPLX.dockerbuild
|
40.8 KB |
sha256:94d5d88aff01f1502ecb1b611532ffb63a2b06ee431b2f7b37ee8415882b11cc
|
|
|
broadinstitute~viral-ngs~B8HOCT.dockerbuild
|
113 KB |
sha256:4a9d050874a4ad532305b1e09522b3d8c3d0fef9723096f73ce8b5a88476fba9
|
|
|
broadinstitute~viral-ngs~EAJI7R.dockerbuild
|
78 KB |
sha256:37ac6c3119d079238c96f116126a2df603e2a08730412e8978dca95db144f8b1
|
|
|
broadinstitute~viral-ngs~M5G2QT.dockerbuild
|
79.3 KB |
sha256:025e15625ec77be0716b32cc84dca167224d6b45a1c405a4aa94fbb8f587ac79
|
|
|
broadinstitute~viral-ngs~QTQMAB.dockerbuild
|
43.4 KB |
sha256:54b73cc339de55d669bfe8aba276396cb24c781235a96e2d7308a595b581a1dc
|
|
|
broadinstitute~viral-ngs~R565ST.dockerbuild
|
111 KB |
sha256:0cd2f3878ddfc2af8fc8e31b3c8e7e34853bee395b19f36d31179e590eef45b6
|
|
|
broadinstitute~viral-ngs~RS3ORS.dockerbuild
|
107 KB |
sha256:e65f184d898c8e56ccee9231840016e021dd16dde0b33b7979079cc358666f98
|
|
|
broadinstitute~viral-ngs~RX1WBX.dockerbuild
|
108 KB |
sha256:5430f6c1aa2169c4346206780176b67e976835b2c019bfb56f4590adb833c760
|
|
|
broadinstitute~viral-ngs~SVHCJ9.dockerbuild
|
117 KB |
sha256:a2baf1f1463d44d399628cb7c16968c2046f7605054c4d73a4a6b03dadffc8db
|
|
|
broadinstitute~viral-ngs~V80ZGI.dockerbuild
|
103 KB |
sha256:885359189b1ed4d2f1472f11d413939f4777131bd7bd9aec6bbdad31dc2024ed
|
|
|
broadinstitute~viral-ngs~YSAF0F.dockerbuild
|
99.9 KB |
sha256:4f41d34b4378d07848407ab5b545b0b48788efec32118a37a94d45839003aafa
|
|
|
broadinstitute~viral-ngs~ZCAWUG.dockerbuild
|
106 KB |
sha256:3c2b4fc9bfa267ef47d94787ce27876779955db991d34af48e645369e15855db
|
|
|
trivy-assemble
|
79.7 KB |
sha256:2e9c501e2aec018d0910369de83b9363f4ad0967e292cd8ae552d5dd19b73267
|
|
|
trivy-baseimage
|
69.4 KB |
sha256:d7917074930abe550f9e255f308b8d76d990c145377570bf86ee968dc9fba386
|
|
|
trivy-classify
|
79.7 KB |
sha256:5aa97d5413911958e72bb87ab6a9e968d825526c1560c33b65a67e51c7d65295
|
|
|
trivy-core
|
75.3 KB |
sha256:69f29c7fe095c7dbffde4db7d896459e7e589d87e9a1daf8f6a1bdabcd70f65d
|
|
|
trivy-mega
|
84.5 KB |
sha256:092a1d12cf30250a5a1cf167cad9ff219169f537717a157a6b78142b39b356e5
|
|
|
trivy-phylo
|
80.5 KB |
sha256:67b5ff3cc0307409b1230e04e7f02b57d8f0317d0de7b64d16f28b003fd176e9
|
|