🚀 Release 1.123.26 #735
Matsuuurelease-publish.yml
on: pull_request
Publish to NPM
7m 4s
build-arm64
7m 29s
Matrix: Publish to DockerHub / build-and-push-docker
Publish to DockerHub
/
Notify Cats on nightly build failure
Publish to DockerHub
/
Create Multi-Arch Manifest
53s
Publish to DockerHub
/
...
/
Security - Scan Docker Image With Trivy
1m 24s
Publish to DockerHub
/
...
/
Security - Scan Docker Image With Trivy
30s
Create a Sentry Release
1m 29s
Trigger a release note
0s
Generate and Attach SBOM to Release
/
Generate and Attach SBOM to Release
Annotations
1 error and 19 warnings
|
Create a GitHub Release
Error 403: Resource not accessible by integration - https://docs.github.com/rest/releases/releases#create-a-release
|
|
Publish to NPM
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061, rharkor/caching-for-turbo@cda201ff2b32699a2ae9f59704db029e3dde4fbd. 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/
|
|
Publish to NPM
The process '/usr/bin/git' failed with exit code 128
|
|
build-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061, rharkor/caching-for-turbo@cda201ff2b32699a2ae9f59704db029e3dde4fbd. 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-arm64
The process '/usr/bin/git' failed with exit code 128
|
|
Publish to DockerHub / Determine Build Context
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 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/
|
|
Publish to DockerHub / Determine Build Context
The process '/usr/bin/git' failed with exit code 128
|
|
Publish to DockerHub / Build App, then Build and Push Docker Image (arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061, rharkor/caching-for-turbo@cda201ff2b32699a2ae9f59704db029e3dde4fbd, useblacksmith/build-push-action@30c71162f16ea2c27c3e21523255d209b8b538c1, useblacksmith/setup-docker-builder@53647ab5afe8827af5623b35bd4302eabd41619f. 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/
|
|
Publish to DockerHub / Build App, then Build and Push Docker Image (arm64)
The process '/usr/bin/git' failed with exit code 128
|
|
Publish to DockerHub / Build App, then Build and Push Docker Image (amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061, rharkor/caching-for-turbo@cda201ff2b32699a2ae9f59704db029e3dde4fbd, useblacksmith/build-push-action@30c71162f16ea2c27c3e21523255d209b8b538c1, useblacksmith/setup-docker-builder@53647ab5afe8827af5623b35bd4302eabd41619f. 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/
|
|
Publish to DockerHub / Build App, then Build and Push Docker Image (amd64)
The process '/usr/bin/git' failed with exit code 128
|
|
Publish to DockerHub / Create Multi-Arch Manifest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435. 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/
|
|
Publish to DockerHub / Create Multi-Arch Manifest
The process '/usr/bin/git' failed with exit code 128
|
|
Publish to DockerHub / Security Scan (runners) / Security - Scan Docker Image With Trivy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, slackapi/slack-github-action@91efab103c0de0a537f72a35f6b8cda0ee76bf0a. 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/
|
|
Publish to DockerHub / Security Scan (runners) / Security - Scan Docker Image With Trivy
The process '/usr/bin/git' failed with exit code 128
|
|
Publish to DockerHub / Security Scan / Security - Scan Docker Image With Trivy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, slackapi/slack-github-action@91efab103c0de0a537f72a35f6b8cda0ee76bf0a. 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/
|
|
Publish to DockerHub / Security Scan / Security - Scan Docker Image With Trivy
The process '/usr/bin/git' failed with exit code 128
|
|
Create a GitHub Release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ncipollo/release-action@1c89adf39833729d8f85a31ccbc451b078733c80. 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/
|
|
Create a Sentry Release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061, rharkor/caching-for-turbo@cda201ff2b32699a2ae9f59704db029e3dde4fbd. 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/
|
|
Create a Sentry Release
The process '/usr/bin/git' failed with exit code 128
|