cluster: allow forwarded messages to be forwarded twice (#1153) #842
svix-jbrownon-push.yml
on: push
ci
/
...
/
Build Server Binary
53s
ci
/
Formatting
14s
ci
/
Check cargo manifests
7s
ci
/
Clippy
38s
ci
/
Validate prek
13s
ci
/
Test
1m 30s
ci
/
Check openapi.json, SDK, and default config freshness
1m 4s
ci
/
Check CRD JSON freshness
22s
ci
/
Operator e2e tests
3m 56s
ci
/
security-audit
33s
java
/
Build Java SDK
32s
javascript
/
Lint JavaScript
10s
python
/
Lint
9s
Matrix: ci / sdk-integration / test-go
Matrix: ci / sdk-integration / test-java
Matrix: ci / sdk-integration / test-javascript
Matrix: ci / sdk-integration / test-python
Matrix: ci / sdk-integration / test-rust
Matrix: docker_publish_cli / build-and-push-image
Matrix: docker_publish_operator / build-and-push-image
Matrix: docker_publish_server / build-and-push-image
docker_publish_cli
/
merge
23s
staging-deploy
3s
Annotations
36 warnings
|
ci / Check CRD JSON freshness
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ubicloud/rust-cache@v2. 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/
|
|
ci / Clippy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ubicloud/rust-cache@v2. 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/
|
|
ci / sdk-integration / Build Server Binary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ubicloud/rust-cache@v2. 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/
|
|
ci / Check openapi.json, SDK, and default config freshness
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ubicloud/rust-cache@v2. 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/
|
|
ci / sdk-integration / Python SDK (3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. 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/
|
|
ci / sdk-integration / Python SDK (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. 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/
|
|
ci / sdk-integration / JavaScript SDK (Node 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/setup-node@v4. 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/
|
|
ci / sdk-integration / JavaScript SDK (Node 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/setup-node@v4. 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/
|
|
ci / Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ubicloud/rust-cache@v2. 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/
|
|
ci / sdk-integration / Go SDK (1.22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/setup-go@v5. 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/
|
|
ci / sdk-integration / Go SDK (1.22)
Restore cache failed: Dependencies file is not found in /home/runner/work/diom/diom. Supported file pattern: go.sum
|
|
ci / sdk-integration / Go SDK (1.23)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/setup-go@v5. 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/
|
|
ci / sdk-integration / Go SDK (1.23)
Restore cache failed: Dependencies file is not found in /home/runner/work/diom/diom. Supported file pattern: go.sum
|
|
ci / sdk-integration / Java SDK (17)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/setup-java@v4. 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/
|
|
ci / sdk-integration / Rust SDK (stable)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. 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/
|
|
ci / sdk-integration / Java SDK (11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/setup-java@v4. 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/
|
|
ci / sdk-integration / Java SDK (21)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/setup-java@v4. 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/
|
|
ci / sdk-integration / Rust SDK (beta)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. 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/
|
|
ci / sdk-integration / Java SDK (8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/setup-java@v4. 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/
|
|
ci / Operator e2e tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ubicloud/rust-cache@v2. 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/
|
|
helm-publish / helm-publish
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/setup-helm@v4, docker/login-action@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/
|
|
docker_publish_cli / build-and-push-image (linux/amd64, ubuntu-24.04-8-cores)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: anchore/scan-action@v6, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@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/
|
|
docker_publish_cli / build-and-push-image (linux/amd64, ubuntu-24.04-8-cores)
Failed minimum severity level. Found vulnerabilities with level 'negligible' or higher
|
|
docker_publish_operator / build-and-push-image (linux/amd64, ubuntu-24.04-8-cores)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: anchore/scan-action@v6, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@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/
|
|
docker_publish_operator / build-and-push-image (linux/amd64, ubuntu-24.04-8-cores)
Failed minimum severity level. Found vulnerabilities with level 'negligible' or higher
|
|
docker_publish_cli / build-and-push-image (linux/arm64, ubuntu-24.04-arm-8-cores)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: anchore/scan-action@v6, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@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/
|
|
docker_publish_cli / build-and-push-image (linux/arm64, ubuntu-24.04-arm-8-cores)
Failed minimum severity level. Found vulnerabilities with level 'negligible' or higher
|
|
docker_publish_cli / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@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/
|
|
docker_publish_operator / build-and-push-image (linux/arm64, ubuntu-24.04-arm-8-cores)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: anchore/scan-action@v6, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@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/
|
|
docker_publish_operator / build-and-push-image (linux/arm64, ubuntu-24.04-arm-8-cores)
Failed minimum severity level. Found vulnerabilities with level 'negligible' or higher
|
|
docker_publish_operator / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@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/
|
|
docker_publish_server / build-and-push-image (linux/arm64, ubuntu-24.04-arm-8-cores)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: anchore/scan-action@v6, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@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/
|
|
docker_publish_server / build-and-push-image (linux/arm64, ubuntu-24.04-arm-8-cores)
Failed minimum severity level. Found vulnerabilities with level 'negligible' or higher
|
|
docker_publish_server / build-and-push-image (linux/amd64, ubuntu-24.04-8-cores)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: anchore/scan-action@v6, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@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/
|
|
docker_publish_server / build-and-push-image (linux/amd64, ubuntu-24.04-8-cores)
Failed minimum severity level. Found vulnerabilities with level 'negligible' or higher
|
|
docker_publish_server / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
digests-svix-diom-cli-private-linux-amd64
|
244 Bytes |
sha256:9e1f57d4e7b50ec76c6be7594641cc5460ebbea94e16f4e40e14dc9c6ef9aab1
|
|
|
digests-svix-diom-cli-private-linux-arm64
|
244 Bytes |
sha256:0c417bd59ecc897bbda069c4504247b3264bcf0fe7614bf5ad289dbc03bdf191
|
|
|
digests-svix-diom-operator-private-linux-amd64
|
244 Bytes |
sha256:71fb188cb37cfe4b6614546c32738c411c0bd1b64cca9c9acd7a838b7992da7e
|
|
|
digests-svix-diom-operator-private-linux-arm64
|
244 Bytes |
sha256:d6961140afbd45db7bf20fbdd1085ab691900b0912baac8cc9cc565c7662f1e9
|
|
|
digests-svix-diom-server-private-linux-amd64
|
244 Bytes |
sha256:36caf861f0e792ecc94d44c31a81b897fe61202b3770809c95b1089d7c29f366
|
|
|
digests-svix-diom-server-private-linux-arm64
|
244 Bytes |
sha256:c980e2d6c20eca8a03db9602195154cdd443f67a65763053e488f1fbb7a0c173
|
|
|
diom-server-binary
|
21.5 MB |
sha256:e1b6efa4a48fc21cdec99ea759f10d39577bbf00e835c5794829c5afc4a34b02
|
|
|
svix~diom~IGIFGD.dockerbuild
|
46.1 KB |
sha256:e636f4e2240d04b17213932bf495cc4fa0ff603b8a1dc4ae345d08a4aacd2a05
|
|
|
svix~diom~JJ1SMZ.dockerbuild
|
40.8 KB |
sha256:1de09f4d8fe2377f203f5c713eaebb585f5b97ebd5b224e40855708487bd5a01
|
|
|
svix~diom~KP1B1X.dockerbuild
|
51.7 KB |
sha256:79799954b2c9f73ecc7a0ffab59a09afe3e4389c76b095d226bbedff1d600233
|
|
|
svix~diom~L8KC9W.dockerbuild
|
54.1 KB |
sha256:a2bb34cebc5e3d4095ab5d313fbb16d37f630ff2e66121504bfe4f791185788b
|
|
|
svix~diom~L9GZHQ.dockerbuild
|
39.4 KB |
sha256:bca2b4787022cd578701873970c5b688151bb429f47cdacee0faffa1f16a3b53
|
|
|
svix~diom~M7PY2T.dockerbuild
|
68.1 KB |
sha256:1968474f3d5d39617e9ca6712d2ae1f6d12e6ae1d2ccdea405d4e35b47691714
|
|
|
svix~diom~MQAVAT.dockerbuild
|
59.5 KB |
sha256:bfc26d044027c9b4632a01f5806fec1aaec58bc54469a3c2675754524eaac0e7
|
|
|
svix~diom~O8VJI4.dockerbuild
|
93 KB |
sha256:b135e995c33c23f3d7d7d9b5d32c485c025a6d1b2dbac5faa42713ab73ccda01
|
|
|
svix~diom~OU3NKG.dockerbuild
|
39.5 KB |
sha256:3b7854ac2c2c010917968684c5c49b351378bf12552357522b78b458ffbff7af
|
|
|
svix~diom~P70XRK.dockerbuild
|
40.9 KB |
sha256:65d65d7bce57f79438c764a8740c3bb88f0da81c6b5490027cee84231b740ff3
|
|
|
svix~diom~WGGRQU.dockerbuild
|
68.9 KB |
sha256:f78c933f20c821973e6c875c08f15c8ac7dccd5c61ddbadd5cd9c157f7ccdd7f
|
|
|
svix~diom~YY7Z3S.dockerbuild
|
45 KB |
sha256:d177984cecff534fd43363f1740307ae15160a1f8295afca6efdbac42f9cc7f1
|
|
|
test-report
|
354 KB |
sha256:c3129804c99ba96f00cb4df0d0dec3dcbc5d402aae0266ff2f48bff5eaa01136
|
|