test: for smctl #569
release-build.yml
on: push
Matrix: build-and-upload-release-artifacts
generate-sbom-and-upload-assets
31s
update-pull-request
6s
Annotations
8 warnings and 3 notices
|
generate-sbom-and-upload-assets
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@4cec3d8aa04e39d1a68397de0c4cd6fb9dce8ec1, anchore/sbom-action@55dc4ee22412511ee8c3142cbea40418e6cec693, anchore/scan-action/download-grype@64a33b277ea7a1215a3c142735a1091341939ff5, anchore/scan-action@64a33b277ea7a1215a3c142735a1091341939ff5, andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6. 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/
|
|
generate-sbom-and-upload-assets
Failed minimum severity level. Found vulnerabilities with level 'critical' or higher
|
|
generate-sbom-and-upload-assets
Failed minimum severity level. Found vulnerabilities with level 'critical' or higher
|
|
generate-sbom-and-upload-assets
Failed minimum severity level. Found vulnerabilities with level 'critical' or higher
|
|
build-and-upload-release-artifacts (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: digicert/code-signing-software-trust-action@9b30180369343eb1ce0dcbebb933cfa3e17b6cc8. 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-and-upload-release-artifacts (macos-latest-large, DESIGNER_MAC_CSC_LINK, DESIGNER_MAC_CSC_K...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: BoundfoxStudios/action-xcode-staple@1e2200b448c6ed4dd44b963ff17d3e340fc6b064, lando/notarize-action@b5c3ef16cf2fbcf2af26dc58c90255ec242abeed. 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-and-upload-release-artifacts (ubuntu-24.04)
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/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, anchore/sbom-action@f8bdd1d8ac5e901a77a92f111440fdb1b593736b, anchore/scan-action/download-grype@f6601287cdb1efc985d6b765bbf99cb4c0ac29d8, anchore/scan-action@f6601287cdb1efc985d6b765bbf99cb4c0ac29d8. 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/
|
|
update-pull-request
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: kt3k/update-pr-description@fef8b17c6648e0daa550d2ed6b5cf140d282574e. 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/
|
|
generate-sbom-and-upload-assets
Grype DB is updated succesfully
|
|
build-and-upload-release-artifacts (windows-latest)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
|
|
build-and-upload-release-artifacts (ubuntu-24.04)
Grype DB is updated successfully
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Linux-X64-artifacts
|
2.47 GB |
sha256:d56fd0bc6f5db4bda0dec79c8ba37a7f5c0527299b059abc712aa54e65ee84a0
|
|
|
Linux-X64-sentry
|
35.2 MB |
sha256:9ea87a90dec78652136949ba2425d262813a9772aa369a694635865c1b705146
|
|
|
Windows-X64-artifacts
|
1.69 GB |
sha256:3b11aba46a04a5b37c767943db85dd87aaec8a18078f7dfe48517c80d61b1cbc
|
|
|
Windows-X64-sentry
|
35.2 MB |
sha256:802cfd9a58d3dfae639e6e0702d60ebfa109084c4df046abc980210198dd6cae
|
|
|
cve-report.json
|
146 Bytes |
sha256:6a30f1d23a616dfab3ea567b8467014093aee8530744092fdd0913a12bb86c92
|
|
|
cve-report.sarif
|
148 Bytes |
sha256:1ccd50e27657651ffbbe76d8e05f92e60c742429d31a364996003221ed88d3e6
|
|
|
image-inso-Linux-X64-cve-report.json
|
19.9 KB |
sha256:dfabae6119cb27ce99f79d6042920238ae3e62f3443f6c220ffabf9fa61219ca
|
|
|
image-inso-Linux-X64-cve-report.sarif
|
8.33 KB |
sha256:ca7fc9823675d129c33d49f341122c4ebcbe44c19f66e60b311b135661b3ce65
|
|
|
image-inso-Linux-X64-sbom.cyclonedx.json
|
193 KB |
sha256:11e7a636351f7799735e4f672fe7536c78da1ba52e4e21daa09d82f2c747f1dc
|
|
|
image-inso-Linux-X64-sbom.spdx.json
|
256 KB |
sha256:83777b2c650e5ccd4c0cb7e9e601917dfdbc0d8ed0d44a561d48f054d01ecf46
|
|
|
macOS-X64-artifacts
|
847 MB |
sha256:641a855d8316bfc380c492286d991627b93219ed78e8fb6d26a28c02ddbe76ba
|
|
|
macOS-X64-sentry
|
35.2 MB |
sha256:b83ef0ee54164081422eb024b00935cd1db6b3a67b35926e2bbbd9ebfade28f4
|
|
|
sbom.cyclonedx.json
|
179 KB |
sha256:cc08d18f4b11fa686871459da8e6806f6c7cfcdf22962df73b8c74e3d9e703e7
|
|
|
sbom.spdx.json
|
309 KB |
sha256:766af8a47c6b2b45ae574477ab1fe9a8b2fe8f3119d0c2b51138fa7e50e10b48
|
|