ZXF: Deploy Production Release #6532
node-flow-deploy-release-artifact.yaml
on: workflow_dispatch
Release [Branch]
/
Validate
1m 23s
Prepare Release [Tag]
Update Hedera Protobufs
0s
Release [Branch]
/
...
/
Publish Production Image (GCP)
2m 49s
Release [Branch]
/
...
/
Publish Production Image (JFrog)
3m 17s
Release [Branch]
/
...
/
Validate Input Version
Release [Branch]
/
...
/
Full Commit History
Release [Branch]
/
...
/
Generate Release Notes File
Release [Tag]
/
...
/
publish-image
Release [Tag]
/
...
/
publish-image
Release [Tag]
/
...
/
Validate Input Version
Release [Branch]
/
...
/
Create Github Release
Release [Tag]
/
...
/
Generate Release Notes File
Release [Tag]
/
...
/
Full Commit History
Trigger Deploy Integration Flow
2m 44s
Release [Tag]
/
Send Release Notifications
Release [Tag]
/
...
/
Create Github Release
Report Production Release Failures
0s
Annotations
11 warnings
|
Release [Branch] / Validate
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, step-security/harden-runner@ec9f2d5744a09debf3a187a3f4f675c53b671911. 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 [Branch] / Build Artifact
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, google-github-actions/setup-gcloud@77e7a554d41e2ee56fc945c52dfd3f33d12def9a, google-github-actions/upload-cloud-storage@7c6e11cb7291594c5dfe0bc1dd9cd905e31e600c, step-security/google-github-auth@40f6deebd366f16c782d7a0ad0844e3b96a032a6, step-security/harden-runner@ec9f2d5744a09debf3a187a3f4f675c53b671911. 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 [Branch] / Publish Production Image / Publish Production Image (GCP)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, docker/login-action@74a5d142397b4f367a81961eba4e8cd7edddf772, docker/setup-qemu-action@5964de0df58d5ad28b04d8fe2e6b80ad47105b91, step-security/google-github-auth@40f6deebd366f16c782d7a0ad0844e3b96a032a6, step-security/harden-runner@ec9f2d5744a09debf3a187a3f4f675c53b671911. 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 [Branch] / Publish Production Image / Publish Production Image (JFrog)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, docker/login-action@74a5d142397b4f367a81961eba4e8cd7edddf772, docker/setup-qemu-action@5964de0df58d5ad28b04d8fe2e6b80ad47105b91, jfrog/setup-jfrog-cli@ff5cb544114ffc152db9cea1cd3d5978d5074946, step-security/harden-runner@ec9f2d5744a09debf3a187a3f4f675c53b671911. 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 [Branch] / Publish Local Node Images
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, docker/login-action@74a5d142397b4f367a81961eba4e8cd7edddf772, docker/setup-qemu-action@5964de0df58d5ad28b04d8fe2e6b80ad47105b91, step-security/google-github-auth@40f6deebd366f16c782d7a0ad0844e3b96a032a6, step-security/harden-runner@ec9f2d5744a09debf3a187a3f4f675c53b671911. 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 [Branch] / Publish to GCP Registry
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00, google-github-actions/setup-gcloud@77e7a554d41e2ee56fc945c52dfd3f33d12def9a, step-security/ghaction-import-gpg@c86c374c0659a6c2d1284bccf8af889e73ce8fe0, step-security/google-github-auth@40f6deebd366f16c782d7a0ad0844e3b96a032a6, step-security/harden-runner@ec9f2d5744a09debf3a187a3f4f675c53b671911. 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/
|
|
Application Archive Missing:
node-zxc-build-release-artifact.yaml#L858
The application archive file is missing; skipping signing.
|
|
No Apps Found:
node-zxc-build-release-artifact.yaml#L829
No apps files were found to include in the application archive.
|
|
Release [Branch] / Validate Production Image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, docker/login-action@74a5d142397b4f367a81961eba4e8cd7edddf772, jfrog/setup-jfrog-cli@ff5cb544114ffc152db9cea1cd3d5978d5074946, step-security/google-github-auth@40f6deebd366f16c782d7a0ad0844e3b96a032a6, step-security/harden-runner@ec9f2d5744a09debf3a187a3f4f675c53b671911. 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/
|
|
Trigger XTS CI Flow
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, step-security/harden-runner@ec9f2d5744a09debf3a187a3f4f675c53b671911, step-security/workflow-dispatch@b4c1dc0afa074d0b4f0e653d3b80d4b2798599aa. 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/
|
|
Trigger Deploy Integration Flow
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, step-security/harden-runner@ec9f2d5744a09debf3a187a3f4f675c53b671911, step-security/workflow-dispatch@b4c1dc0afa074d0b4f0e653d3b80d4b2798599aa. 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 | |
|---|---|---|---|
|
Production Image Manifests
|
83.8 KB |
sha256:421c6eb0b3e3da77694dd85b28772c25ea04a0f4da7835f52536c7e17e55127b
|
|
|
hiero-ledger~hiero-consensus-node~65S7LT.dockerbuild
|
112 KB |
sha256:d6b12cc3068737695a5458a951cd2398e47dfdc5040dc7f6b22e69045741da0b
|
|
|
hiero-ledger~hiero-consensus-node~D0BP4L.dockerbuild
|
123 KB |
sha256:fb174d1bebe61949946f7434178155c15791e7db5df47adde953d43e1a91007d
|
|
|
hiero-ledger~hiero-consensus-node~JPL10O.dockerbuild
|
164 KB |
sha256:5a2a4439a355bb3f44b4994b4ece5bc670fc3bfee15a61f8e3cb721ebef2069e
|
|
|
hiero-ledger~hiero-consensus-node~K27Z1B.dockerbuild
|
159 KB |
sha256:38038a1e2e8cfae515013464a1aace858a839ee0b0d63248813754fd59ee6d4f
|
|
|
hiero-ledger~hiero-consensus-node~NHVE3H.dockerbuild
|
189 KB |
sha256:66ca7aa2268b7e0de4ff2b246afbaf2562d3bc535fb7231da80f82916af47d85
|
|
|
node-build-artifacts-0.73.0-release-0.73.xafa1f8e-afa1f8ef145fac02abc23f55a00ee16fe387cb53
|
109 MB |
sha256:2aa4443afc8b8d6373ac354be802be74f092e5e2b732582dc64c18f7b3a521e8
|
|
|
version.txt
|
163 Bytes |
sha256:9a92eed5e359c9974c490be3b91142e1e041d0632cb2e991bd97158148b54c18
|
|