Upgrade go1.25.7 to go1.26.1 #1553
Ram-srinipre-merge.yml
on: pull_request
Annotations
9 errors and 20 warnings
|
pre-merge-pipeline (maintenance) / run-repo-pipelines
Process completed with exit code 2.
|
|
pre-merge-pipeline (maintenance) / run-repo-pipelines
var-naming: avoid package names that conflict with Go standard library package names (revive)
|
|
pre-merge-pipeline (os-resource) / run-repo-pipelines
Process completed with exit code 2.
|
|
pre-merge-pipeline (os-resource) / run-repo-pipelines
var-naming: avoid package names that conflict with Go standard library package names (revive)
|
|
pre-merge-pipeline (networking) / run-repo-pipelines
Process completed with exit code 2.
|
|
pre-merge-pipeline (networking) / run-repo-pipelines
var-naming: avoid package names that conflict with Go standard library package names (revive)
|
|
pre-merge-pipeline (telemetry) / run-repo-pipelines
Process completed with exit code 2.
|
|
pre-merge-pipeline (telemetry) / run-repo-pipelines
var-naming: avoid package names that conflict with Go standard library package names (revive)
|
|
final-check
Process completed with exit code 1.
|
|
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 (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 (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 (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 (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 (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 (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 (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 (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/
|
|
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 (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 (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 (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 (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 (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 (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 (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 (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 (host) / run-repo-pipelines
No files were found with the provided path: docker-images. No artifacts will be uploaded.
|
|
pre-merge-pipeline (attestationstatus) / run-repo-pipelines
No files were found with the provided path: docker-images. No artifacts will be uploaded.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
gitleaks-results-4wyoea-attestationstatus
|
175 Bytes |
sha256:da9499ac2e7b6b76a64fb738b841f0a9c0ff50b216954caa1b855531b1ea5eb7
|
|
|
gitleaks-results-6ykj0n-os-resource
|
175 Bytes |
sha256:e4224c81b2334d85857ad9441db91e44129263ec912fab36424a13ae57f0aac5
|
|
|
gitleaks-results-a55g6q-networking
|
175 Bytes |
sha256:1ace2983967e908c3e916a7b258cf110bfe7620969e44967fceb792c61c4d0f2
|
|
|
gitleaks-results-a7lkwz-maintenance
|
175 Bytes |
sha256:40c41487360635feecf5d81b21846a7eacf32ba18074b38c1db964b9692e6510
|
|
|
gitleaks-results-r2nozb-host
|
175 Bytes |
sha256:44d4a7653ded2a949ce5b7f5db2c972e83af36418c927d7df20ba0fca6147b80
|
|
|
gitleaks-results-wwrdbn-telemetry
|
175 Bytes |
sha256:d40b8e1e3e1d91d6c645f7b156ff2832ec77d8558a2253c2b52311b31a9cbcf5
|
|
|
trivy-config-scan-attestationstatus
|
1.09 KB |
sha256:ac4eb480f67fe5ac39a1e2a060d8b88b2ae6f13076440e77a083f0b5ac40eeb1
|
|
|
trivy-config-scan-host
|
1.06 KB |
sha256:90694dd2719ba62762f98eef6a6b8ebb4089f6d8be3f8d2b132150aff7ac2a2c
|
|
|
trivy-config-scan-maintenance
|
1.08 KB |
sha256:2b53dcda9bfe80af23cddf17f34adbc93f50a35451dbcd7fbdc4c285562e1cf2
|
|
|
trivy-config-scan-networking
|
1.07 KB |
sha256:c491264bcd49abe1e448d21c54b2d0c56aaf827529f962f4d94ec4f136abb413
|
|
|
trivy-config-scan-os-resource
|
509 Bytes |
sha256:d1921ac76779b235802413483b04098aab5a838d5efd72cff7c1ee59d6603cb2
|
|
|
trivy-config-scan-telemetry
|
1.07 KB |
sha256:88733d771b972e4e835086ac66196c3a1d136f9c3bae809a5416e4a40c549f8a
|
|
|
trivy-fs-scan-report-attestationstatus
|
532 Bytes |
sha256:c4816d7aa209ba873f7e86c85a6faae9355d928c376efa7f1c1bdf4e5d236b8e
|
|
|
trivy-fs-scan-report-host
|
501 Bytes |
sha256:d68adab839c11132030d85c12d6751d76783f744f247f34eeecb4f63ae7308f7
|
|
|
trivy-fs-scan-report-maintenance
|
519 Bytes |
sha256:797a2b55a67e414446b09ac253c981add68127fd7510d0b72fcd374a51c7b765
|
|
|
trivy-fs-scan-report-networking
|
516 Bytes |
sha256:050925f903bd841b199239d72b9ae571e8abc53aafa59912c84fa005cb8ca127
|
|
|
trivy-fs-scan-report-os-resource
|
519 Bytes |
sha256:f951da8d4a7050e9815757881f5eb28762dbf13e07a1ff2aba144d60ebf9446c
|
|
|
trivy-fs-scan-report-telemetry
|
514 Bytes |
sha256:7eb8fe2a6bbe147be81a7e9c82142166a8fbf3f7f0c5e75cd743575c9971a963
|
|
|
zizmor-scan-report-attestationstatus
|
593 Bytes |
sha256:2965327b50e198fccc1e30f5103e8cc0ba0bf6b48ea116a0353e66963699b124
|
|
|
zizmor-scan-report-host
|
593 Bytes |
sha256:759228d6a96eb8a790b60d960220a15c074f165c6dd114e0ef39a3af18a36a59
|
|
|
zizmor-scan-report-maintenance
|
593 Bytes |
sha256:be592f85e3de42e960e04cf1bf10017f812913ba62fe1ed0ed0dd22142808f07
|
|
|
zizmor-scan-report-networking
|
593 Bytes |
sha256:be592f85e3de42e960e04cf1bf10017f812913ba62fe1ed0ed0dd22142808f07
|
|
|
zizmor-scan-report-os-resource
|
593 Bytes |
sha256:be592f85e3de42e960e04cf1bf10017f812913ba62fe1ed0ed0dd22142808f07
|
|
|
zizmor-scan-report-telemetry
|
593 Bytes |
sha256:759228d6a96eb8a790b60d960220a15c074f165c6dd114e0ef39a3af18a36a59
|
|