[gomod] Bump go.opentelemetry.io/otel/sdk from 1.41.0 to 1.43.0 in /e… #82
Ram-srinipost-merge-exporters-inventory.yml
on: push
post-merge-pipeline
/
sanitize-project-folder
3s
post-merge-pipeline
/
version-bump
6s
post-merge-pipeline
/
trivy-filesystem-scan
24s
post-merge-pipeline
/
trivy-config-scan
22s
post-merge-pipeline
/
secrets-gitleaks-scan
27s
post-merge-pipeline
/
zizmor-scan
18s
post-merge-pipeline
/
bandit
22s
post-merge-pipeline
/
...
/
notify
Matrix: post-merge-pipeline / sign-binaries
Matrix: post-merge-pipeline / sign-images
Matrix: post-merge-pipeline / scan-images
Annotations
6 warnings
|
post-merge-pipeline / bandit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, github/codeql-action/upload-sarif@1b549b9259bda1cb5ddde3b41741a82a2d15a841. 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/
|
|
post-merge-pipeline / 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/
|
|
post-merge-pipeline / 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/
|
|
post-merge-pipeline / secrets-gitleaks-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, github/codeql-action/upload-sarif@1b549b9259bda1cb5ddde3b41741a82a2d15a841. 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/
|
|
post-merge-pipeline / scan-images (080137407410.dkr.ecr.us-west-2.amazonaws.com/edge-orch/infra/exporter:1.27.0-dev)
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/
|
|
post-merge-pipeline / scan-images (080137407410.dkr.ecr.us-west-2.amazonaws.com/edge-orch/infra/exporter:main)
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 | |
|---|---|---|---|
|
bandit-results-e48snb
|
942 Bytes |
sha256:8211da5e3bb6eebb50dd249d5d82e3f8773cb3de014ab47ce90983584faca0d9
|
|
|
built-binaries-fce8174803ee5b26ffed9bd74c7ebc020ed7413f
|
13.4 MB |
sha256:ae389795effe8e0f79e119901a74d470a9c62b1d98ea9120ec8bfbf665a1d21e
|
|
|
built-binaries-fce8174803ee5b26ffed9bd74c7ebc020ed7413f-exporter-d9264208-0
|
6.73 KB |
sha256:d9b02235b0f7e7a1d5ed58fc5206af844b548b9e5516ceadaabbaaa9a50ecda1
|
|
|
cosign-binary-0968a1
|
6.73 KB |
sha256:d9b02235b0f7e7a1d5ed58fc5206af844b548b9e5516ceadaabbaaa9a50ecda1
|
|
|
cosign-image-07970e
|
690 Bytes |
sha256:70c11cc80eebebf8b8c0c595c6fc569ad0a837ab0df7e36bc18aed226fbdeda2
|
|
|
docker-images-exporters-inventory
|
370 MB |
sha256:b56ede057874df34baf15c0353863a41f382eeecd95c8e0862400a1c1df97b07
|
|
|
gitleaks-results-recx9b-exporters-inventory
|
7.67 KB |
sha256:dba451b9d8287b56368221bc293a3000f57b1226b0e495c0b3d72d549b1a7422
|
|
|
trivy-config-scan-exporters-inventory
|
1.1 KB |
sha256:0b52be5e96f49c6ea3c2b523db1a113679134cb6a13522174f45bfbcbe731244
|
|
|
trivy-fs-scan-report-fs-exporters-inventory
|
1.35 KB |
sha256:4a1f54fed0b56b2694ada1d8b675883059462968f222ee204f849d60091e1ff2
|
|
|
trivy-image-vuln-080137407410.dkr.ecr.us-west-2.amazonaws.com_edge-orch_infra_exporter_1.27.0-dev
|
4.03 KB |
sha256:7089fac557e3473bc6e3e02c8febcc605cee171e9b75a7bcbe372131d6a229df
|
|
|
trivy-image-vuln-080137407410.dkr.ecr.us-west-2.amazonaws.com_edge-orch_infra_exporter_main
|
4.02 KB |
sha256:0d7fa2ac6acfbe16030969e443802149a8f3093ed540cce849e9e47898506032
|
|
|
trivy-scan-report-sbom-exporters-inventory
|
27.8 KB |
sha256:08ea73d5d0a56d9b6b5eda203a8c8ab2c575e59f30d9b905e5607837e73955c5
|
|