Upgrade go1.25.7 to go1.26.1 #1529
jkossakpre-merge.yml
on: pull_request
Annotations
20 errors and 18 warnings
|
pre-merge-pipeline (os-resource) / run-repo-pipelines
Canceling since a higher priority waiting request for Pre-Merge CI Pipeline-refs/pull/549/merge exists
|
|
pre-merge-pipeline (os-resource) / run-repo-pipelines
The operation was canceled.
|
|
pre-merge-pipeline (telemetry) / run-repo-pipelines
Canceling since a higher priority waiting request for Pre-Merge CI Pipeline-refs/pull/549/merge exists
|
|
pre-merge-pipeline (telemetry) / run-repo-pipelines
The operation was canceled.
|
|
pre-merge-pipeline (host) / run-repo-pipelines
Canceling since a higher priority waiting request for Pre-Merge CI Pipeline-refs/pull/549/merge exists
|
|
pre-merge-pipeline (host) / run-repo-pipelines
The operation was canceled.
|
|
pre-merge-pipeline (networking) / run-repo-pipelines
Canceling since a higher priority waiting request for Pre-Merge CI Pipeline-refs/pull/549/merge exists
|
|
pre-merge-pipeline (networking) / run-repo-pipelines
The operation was canceled.
|
|
pre-merge-pipeline (attestationstatus) / run-repo-pipelines
Canceling since a higher priority waiting request for Pre-Merge CI Pipeline-refs/pull/549/merge exists
|
|
pre-merge-pipeline (attestationstatus) / run-repo-pipelines
The operation was canceled.
|
|
pre-merge-pipeline (maintenance) / run-repo-pipelines
Canceling since a higher priority waiting request for Pre-Merge CI Pipeline-refs/pull/549/merge exists
|
|
pre-merge-pipeline (maintenance) / run-repo-pipelines
The operation was canceled.
|
|
final-check
Process completed with exit code 1.
|
|
Pre-Merge CI Pipeline
Canceling since a higher priority waiting request for Pre-Merge CI Pipeline-refs/pull/549/merge exists
|
|
Pre-Merge CI Pipeline
Canceling since a higher priority waiting request for Pre-Merge CI Pipeline-refs/pull/549/merge exists
|
|
Pre-Merge CI Pipeline
Canceling since a higher priority waiting request for Pre-Merge CI Pipeline-refs/pull/549/merge exists
|
|
Pre-Merge CI Pipeline
Canceling since a higher priority waiting request for Pre-Merge CI Pipeline-refs/pull/549/merge exists
|
|
Pre-Merge CI Pipeline
Canceling since a higher priority waiting request for Pre-Merge CI Pipeline-refs/pull/549/merge exists
|
|
Pre-Merge CI Pipeline
Canceling since a higher priority waiting request for Pre-Merge CI Pipeline-refs/pull/549/merge exists
|
|
Pre-Merge CI Pipeline
Canceling since a higher priority waiting request for Pre-Merge CI Pipeline-refs/pull/549/merge exists
|
|
pre-merge-pipeline (maintenance) / trivy-config-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
|
pre-merge-pipeline (attestationstatus) / trivy-config-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
|
pre-merge-pipeline (os-resource) / trivy-filesystem-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
|
pre-merge-pipeline (maintenance) / trivy-critical-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
|
pre-merge-pipeline (host) / trivy-config-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
|
pre-merge-pipeline (telemetry) / trivy-critical-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
|
pre-merge-pipeline (networking) / trivy-critical-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
|
pre-merge-pipeline (maintenance) / trivy-filesystem-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
|
pre-merge-pipeline (attestationstatus) / trivy-critical-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
|
pre-merge-pipeline (telemetry) / trivy-config-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
|
pre-merge-pipeline (networking) / trivy-filesystem-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
|
pre-merge-pipeline (host) / trivy-critical-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
|
pre-merge-pipeline (os-resource) / trivy-config-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
|
pre-merge-pipeline (telemetry) / trivy-filesystem-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
|
pre-merge-pipeline (networking) / trivy-config-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
|
pre-merge-pipeline (attestationstatus) / trivy-filesystem-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
|
pre-merge-pipeline (os-resource) / trivy-critical-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
|
pre-merge-pipeline (host) / trivy-filesystem-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
gitleaks-results-9htdsh-attestationstatus
Expired
|
175 Bytes |
sha256:773eb1b7b330bfa0cbaf48b3a3faca1b6fbd009876aff94815f5726caec46d18
|
|
|
gitleaks-results-iioocb-networking
Expired
|
175 Bytes |
sha256:c81323b65a5e1f19f385c335ad221f25fe775adba38502faae4c2a61fbc60e33
|
|
|
gitleaks-results-radezm-telemetry
Expired
|
175 Bytes |
sha256:c5263d645e874390f90997c88ddc1c411844bcb0b9b6ca88f0361f0739917b8a
|
|
|
gitleaks-results-sirnah-os-resource
Expired
|
175 Bytes |
sha256:fc2e3e259d2da552e5f9ad9c7ae33802488daf4b29ba4edfdc0a6bba9d0c0da4
|
|
|
gitleaks-results-tazvdd-maintenance
Expired
|
175 Bytes |
sha256:6ac357f5bedc42b8e9b6f16d8112ee205933defa30981d125be7a6fe638a8304
|
|
|
gitleaks-results-ugblpf-host
Expired
|
175 Bytes |
sha256:52353ad5fca985071b0ccae6bb507d4297deb9b27f54a21f78cdc7733d2b372e
|
|
|
trivy-config-scan-attestationstatus
|
1.09 KB |
sha256:b1cb3a9dc3eec3400cef2db964854ea4149c2e6515955137cf912f2c96496b04
|
|
|
trivy-config-scan-host
|
1.06 KB |
sha256:e78c3fed76ed3b065158242739b0625447be71367a075b9e204cc4b1d85fa87d
|
|
|
trivy-config-scan-maintenance
|
1.08 KB |
sha256:553e56c2e71cd13c5153c1facee8b5f3205a640a8b201f734bf4dbcff9e1738f
|
|
|
trivy-config-scan-networking
|
1.07 KB |
sha256:6ce40f26e634c35ab6b3df400b8f664cdfc4ec4aa2d75b51ee874acc2be07a65
|
|
|
trivy-config-scan-os-resource
|
509 Bytes |
sha256:94f45a0116154eb5c83afcbfb872dcce86544091725c857b708b093ecfa13c10
|
|
|
trivy-config-scan-telemetry
|
1.07 KB |
sha256:2811776864724623e42bbb01fa255722c89b71c6ccd58da0f339d2ccb273c7d6
|
|
|
trivy-fs-scan-report-attestationstatus
|
532 Bytes |
sha256:d87a77f2ddb55f911619b7d0d1027d1a16542a25950a5e3289c3e9b0c75686cb
|
|
|
trivy-fs-scan-report-host
|
501 Bytes |
sha256:7b0bd0aa575092014dd2b19d8674d8af235d4e0c657e47fb76c2ae6e41615105
|
|
|
trivy-fs-scan-report-maintenance
|
519 Bytes |
sha256:59f21a344a9eafbba9875af7c42bb0a878e649f33d3706d696251038ff5ccd86
|
|
|
trivy-fs-scan-report-networking
|
516 Bytes |
sha256:31b91cc8e4c548bfde4762b43706e8add636528c4baa8e3d9b8a8894da302732
|
|
|
trivy-fs-scan-report-os-resource
|
519 Bytes |
sha256:38181cde7c3e286ecd35a7c63e73ae1cbb1d26a3e17805644c94349f825de0a1
|
|
|
trivy-fs-scan-report-telemetry
|
514 Bytes |
sha256:b9f35f13bd2e71ec3b8a7308a290573a4fbe6e4a37ba7bfa5235d8a4c829e8ca
|
|
|
zizmor-scan-report-attestationstatus
|
593 Bytes |
sha256:a4a89a83e4e81052ca1e8405908f82fc388290eb7faf4061380652134d89b26e
|
|
|
zizmor-scan-report-host
|
593 Bytes |
sha256:a4a89a83e4e81052ca1e8405908f82fc388290eb7faf4061380652134d89b26e
|
|
|
zizmor-scan-report-maintenance
|
593 Bytes |
sha256:ada36dd3d02e187d1237944b2cfc162d3e1945e711dd45edb6e553ac573e52d5
|
|
|
zizmor-scan-report-networking
|
593 Bytes |
sha256:a4a89a83e4e81052ca1e8405908f82fc388290eb7faf4061380652134d89b26e
|
|
|
zizmor-scan-report-os-resource
|
593 Bytes |
sha256:6ce0d5c490a68c2f3952e59cc92761855c2ba7f5b35b3ba15e0863784fb7c311
|
|
|
zizmor-scan-report-telemetry
|
593 Bytes |
sha256:6ce0d5c490a68c2f3952e59cc92761855c2ba7f5b35b3ba15e0863784fb7c311
|
|