Build gems #3
bangseongbeombuild-gems.yml
on: workflow_dispatch
ci-data
4s
source-gem
1m 22s
Matrix: cross-gem
Annotations
16 errors and 8 warnings
|
Compile native gem for aarch64-mingw-ucrt
Process completed with exit code 1.
|
|
Compile native gem for aarch64-mingw-ucrt
❌ Platform aarch64-mingw-ucrt is not supported, please use one of:
|
|
Compile native gem for x64-mingw-ucrt
The strategy configuration was canceled because "cross-gem.aarch64-mingw-ucrt" failed
|
|
Compile native gem for x64-mingw-ucrt
The operation was canceled.
|
|
Compile native gem for x86_64-darwin
The strategy configuration was canceled because "cross-gem.aarch64-mingw-ucrt" failed
|
|
Compile native gem for x86_64-darwin
The operation was canceled.
|
|
Compile native gem for aarch64-linux-musl
The strategy configuration was canceled because "cross-gem.aarch64-mingw-ucrt" failed
|
|
Compile native gem for aarch64-linux-musl
The operation was canceled.
|
|
Compile native gem for x86_64-linux
The strategy configuration was canceled because "cross-gem.aarch64-mingw-ucrt" failed
|
|
Compile native gem for x86_64-linux
The operation was canceled.
|
|
Compile native gem for arm64-darwin
The strategy configuration was canceled because "cross-gem.aarch64-mingw-ucrt" failed
|
|
Compile native gem for arm64-darwin
The operation was canceled.
|
|
Compile native gem for aarch64-linux
The strategy configuration was canceled because "cross-gem.aarch64-mingw-ucrt" failed
|
|
Compile native gem for aarch64-linux
The operation was canceled.
|
|
Compile native gem for x86_64-linux-musl
The strategy configuration was canceled because "cross-gem.aarch64-mingw-ucrt" failed
|
|
Compile native gem for x86_64-linux-musl
The operation was canceled.
|
|
Compile native gem for aarch64-mingw-ucrt
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, oxidize-rb/actions/post-run@v1. 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/
|
|
Compile native gem for x64-mingw-ucrt
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, oxidize-rb/actions/post-run@v1. 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/
|
|
Compile native gem for x86_64-darwin
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, oxidize-rb/actions/post-run@v1. 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/
|
|
Compile native gem for aarch64-linux-musl
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, oxidize-rb/actions/post-run@v1. 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/
|
|
Compile native gem for x86_64-linux
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, oxidize-rb/actions/post-run@v1. 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/
|
|
Compile native gem for arm64-darwin
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, oxidize-rb/actions/post-run@v1. 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/
|
|
Compile native gem for aarch64-linux
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, oxidize-rb/actions/post-run@v1. 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/
|
|
Compile native gem for x86_64-linux-musl
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, oxidize-rb/actions/post-run@v1. 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 | |
|---|---|---|---|
|
source-gem
|
12.1 KB |
sha256:5a23a7c1978411a647506610a30419fec886ed054e1128bb2d988c6bdc609752
|
|