Skip to content

chore: release v0.3.4 — use Recreate deployment strategy for RWO PVC #11

chore: release v0.3.4 — use Recreate deployment strategy for RWO PVC

chore: release v0.3.4 — use Recreate deployment strategy for RWO PVC #11

Triggered via push March 18, 2026 14:57
Status Success
Total duration 2m 45s
Artifacts 5

release.yaml

on: push
release-controller
2m 24s
release-controller
release-engine-claude-code
1m 16s
release-engine-claude-code
release-engine-codex
1m 39s
release-engine-codex
release-engine-opencode
1m 25s
release-engine-opencode
Release Helm chart
10s
Release Helm chart
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
release-engine-claude-code
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, 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. 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/
release-engine-opencode
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, 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. 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/
release-engine-codex
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, 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. 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/
release-controller
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, anchore/sbom-action/download-syft@v0, 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. 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/
Release Helm chart
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, azure/setup-helm@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
controller-sbom Expired
86.6 KB
sha256:9aeba95b6d538cd293e345200ea70984de3d25c07cc9b7fc968ce6fae42c3a28
unitaryai~osmia~3TCVKA.dockerbuild Expired
73.1 KB
sha256:1c3ffa4189f032d3cef4165c2decd2794a4d315feb7594cca09dfbcf05a28e17
unitaryai~osmia~ACVRMJ.dockerbuild Expired
79.3 KB
sha256:b96c6f0498f9229c5a47d4830647b23f4cf7f3b9dea0bc7385e1738f49781ad5
unitaryai~osmia~OM1NUN.dockerbuild Expired
94.9 KB
sha256:d8c99a5895859158f19262b7638aa8db9046f0ead1bbd15cee3d31a57d84601c
unitaryai~osmia~TDLIWT.dockerbuild Expired
72 KB
sha256:7bcb823a70f3ceafcd7f6b5d3b21b4533360b0f0a8d23476d47d9b1a9888586b