Enhance server clustering support and configuration #2895
goldflagdocker-publish.yml
on: pull_request
Matrix: Build Backend Images
Matrix: Build Client Images
Merge & Push Multi-arch Manifests
21s
Annotations
5 warnings
|
Build Backend Images (ubuntu-latest, linux/amd64)
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, 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/
|
|
Build Backend Images (ubuntu-24.04-arm, linux/arm64)
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, 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/
|
|
Build Client Images (ubuntu-24.04-arm, linux/arm64)
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, 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/
|
|
Build Client Images (ubuntu-latest, linux/amd64)
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, 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/
|
|
Merge & Push Multi-arch Manifests
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. 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-backend-linux-amd64
Expired
|
213 Bytes |
sha256:5b9b7a988e7fd2cf085c0b1cb4b481e9ec5574398d37e6b840a6c17cc91e1bd2
|
|
|
digests-backend-linux-arm64
Expired
|
212 Bytes |
sha256:c5b7c632ead0adff4c85c471505bf7fefaf14900286d6568f350b0ee57f3855e
|
|
|
digests-client-linux-amd64
Expired
|
211 Bytes |
sha256:4515506b39a37fba8bc70d5a882456aa6c3e6382563ba2e8e900f238ed0f5ffa
|
|
|
digests-client-linux-arm64
Expired
|
211 Bytes |
sha256:e7128f11a704e4d91937550464dea8400ecad4e202711d2dcda956429d34e2ab
|
|
|
rybbit-io~rybbit~IO80SS.dockerbuild
|
67.8 KB |
sha256:f12e37f9b40027679c003c4ff3fb60a3614bd7efbbd80f6d5e7ef39fc64ae133
|
|
|
rybbit-io~rybbit~M4ZJD8.dockerbuild
|
56 KB |
sha256:274014867c501a34a9850c241f70bcf17b411416b6de2343d3b185645a785464
|
|
|
rybbit-io~rybbit~OODXD6.dockerbuild
|
56 KB |
sha256:919c872a48231ad009f3cdd1a8fe019b8a950e71085e5826fe79ac461320f367
|
|
|
rybbit-io~rybbit~TSA8HI.dockerbuild
|
65.4 KB |
sha256:4e603b82a93afb26c63005e0e7f94ef21e209fd1f18e341e8cdf506e5dfd98b7
|
|