Skip to content

Bump version to 0.2.0 #10

Bump version to 0.2.0

Bump version to 0.2.0 #10

Triggered via push May 23, 2026 14:30
Status Success
Total duration 4m 16s
Artifacts 6

release.yml

on: push
Matrix: build-linux
Build – macOS (arm64 + x64)
2m 15s
Build – macOS (arm64 + x64)
Publish to npm
59s
Publish to npm
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 12 warnings
Publish to npm: ts/proxy.ts#L157
Property 'emit' does not exist on type 'SymphonyProxy'.
Publish to npm: ts/proxy.ts#L45
Cannot find name 'require'. Do you need to install type definitions for node? Try `npm i --save-dev @types/node` and then add 'node' to the types field in your tsconfig.
Publish to npm: ts/proxy.ts#L33
Cannot find name '__dirname'.
Publish to npm: ts/proxy.ts#L32
Cannot find name '__dirname'.
Publish to npm: ts/proxy.ts#L31
Cannot find name '__dirname'.
Publish to npm: ts/proxy.ts#L30
Cannot find name '__dirname'.
Publish to npm: ts/proxy.ts#L26
Cannot find name 'process'. Do you need to install type definitions for node? Try `npm i --save-dev @types/node` and then add 'node' to the types field in your tsconfig.
Publish to npm: ts/proxy.ts#L25
Cannot find name 'process'. Do you need to install type definitions for node? Try `npm i --save-dev @types/node` and then add 'node' to the types field in your tsconfig.
Publish to npm: ts/proxy.ts#L2
Cannot find name 'node:path'. Do you need to install type definitions for node? Try `npm i --save-dev @types/node` and then add 'node' to the types field in your tsconfig.
Publish to npm: ts/proxy.ts#L1
Cannot find name 'node:events'. Do you need to install type definitions for node? Try `npm i --save-dev @types/node` and then add 'node' to the types field in your tsconfig.
Build – macOS (arm64 + x64)
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@v4, actions/setup-node@v4, actions/upload-artifact@v4. 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/
Build – macOS (arm64 + x64)
The process '/opt/homebrew/bin/git' failed with exit code 128
Build – x86_64-unknown-linux-gnu
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@v4, actions/upload-artifact@v4. 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/
Build – x86_64-unknown-linux-gnu
The process '/usr/bin/git' failed with exit code 128
Build – aarch64-unknown-linux-gnu
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@v4, actions/upload-artifact@v4. 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/
Build – aarch64-unknown-linux-gnu
The process '/usr/bin/git' failed with exit code 128
Build – x86_64-unknown-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@v4, actions/checkout@v4, actions/upload-artifact@v4. 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/
Build – x86_64-unknown-linux-musl
The process '/usr/bin/git' failed with exit code 128
Build – aarch64-unknown-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@v4, actions/checkout@v4, actions/upload-artifact@v4. 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/
Build – aarch64-unknown-linux-musl
The process '/usr/bin/git' failed with exit code 128
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@v4, actions/download-artifact@v4, actions/setup-node@v4. 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/
Publish to npm
The process '/usr/bin/git' failed with exit code 128

Artifacts

Produced during runtime
Name Size Digest
symphony.darwin-arm64.node
1.25 MB
sha256:9ed44ac30cbb5c5105e6181e856ff5914ee48a28403a6fc69a9e05de0aacf922
symphony.darwin-x64.node
1.33 MB
sha256:9a78c0cbe8cba11ae3e98e56318214f945e68e8c1b7496971759b24d56980c5b
symphony.linux-arm64-gnu.node
1.29 MB
sha256:20108e6ba7ab98e47985eb6ceba39e4825a96da045e98f6ef63126e65b6aa2d4
symphony.linux-arm64-musl.node
1.32 MB
sha256:18c7b21a7091e898ae97e82a5a638a530eb5e894f4a368dab421aa6ceb688ff5
symphony.linux-x64-gnu.node
1.38 MB
sha256:36cc901154673a04da1215598487511af4f16b6d7e43ac2675c175e3970188f1
symphony.linux-x64-musl.node
1.38 MB
sha256:f5fbcd1890bdad6bacbbac5c980c5607a9e4ab2da970865383f17a305988b0d4