Skip to content
release

Fix segfault in JS_NewSymbol with NULL description and align with ES semantics #1098

Sign in to view logs

Fix segfault in JS_NewSymbol with NULL description and align with ES semantics

Fix segfault in JS_NewSymbol with NULL description and align with ES semantics #1098

Triggered via pull request April 11, 2026 10:38
@bnoordhuisbnoordhuis
synchronize #1447
engsr6982:master
Status Success
Total duration 10m 34s
Artifacts 10

release.yml

on: pull_request
Matrix: linux
Matrix: windows
check_meson_version
0s
check_meson_version
macos
33s
macos
wasi
43s
wasi
upload-to-release
upload-to-release
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
linux (x86)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: webiny/action-post-run@3.1.0. 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/
linux (x86_64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: webiny/action-post-run@3.1.0. 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/
linux (armv7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: webiny/action-post-run@3.1.0. 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/
linux (aarch64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: webiny/action-post-run@3.1.0. 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/
linux (riscv64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: webiny/action-post-run@3.1.0. 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
qjs-darwin
2.03 MB
sha256:9ce3fb00d428fe3d13057419a2b6cb307dcd3e1150c3cb956fdbf94b99bc8fa7
qjs-linux-aarch64
1.93 MB
sha256:abf3cb4211ed87cc86a02127a938e65c214ec680f22814ee997840a36c051ee3
qjs-linux-armv7
1.76 MB
sha256:df2fdf7486cd1bc99a93e6b0c231c895dc1d5da77f0356c99d3bc6a37d3ea3cb
qjs-linux-riscv64
2.01 MB
sha256:ce64716749cfb0211b705511726969852f1624478b8b915d9fd896b32d530323
qjs-linux-x86
1.97 MB
sha256:7c44cc8699f15cda32dbafd0cebb7a76ce0ec0672e1bfc2de8e0cc1fc9a7cd43
qjs-linux-x86_64
1.93 MB
sha256:5cf33ffb0b36332fe383146b1ce2a471688b32894f27eb441cfc66a6a10c268a
qjs-wasi
1020 KB
sha256:d0d7cd7675cd5ee34797f0c0fcd32dc1f15624f3060113f11741f56f618c3e35
qjs-windows-x86
1.5 MB
sha256:972277e663c7e99fee9fe11b9b3aae332f19daf81472290ffb5502a84a6fd8c0
qjs-windows-x86_64
1.5 MB
sha256:4e4631a8517b8b664a250c1017a3e529ce54f87ed5e6efbb75d60019a9d7c8aa
quickjs-amalgam.zip
513 KB
sha256:ab4680209c6401a3c4abd33b5e177335b8c55c6acdd6ddd05b899bebc823728a