Skip to content

Add performance lint module, first_character/with_das_string builtins, optimize character_at #7295

Add performance lint module, first_character/with_das_string builtins, optimize character_at

Add performance lint module, first_character/with_das_string builtins, optimize character_at #7295

Triggered via pull request March 21, 2026 22:46
@borisbatborisbat
synchronize #2315
string-lint
Status Cancelled
Total duration 7m 46s
Artifacts

wasm_build.yml

on: pull_request
pre_job
7s
pre_job
Matrix: wasm_build
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 4 warnings
wasm_build (linux, 64, Release)
Canceling since a higher priority waiting request for wasm_build-2315 exists
wasm_build (linux, 64, Release)
The operation was canceled.
wasm_build (windows, 64, Release)
Canceling since a higher priority waiting request for wasm_build-2315 exists
wasm_build (windows, 64, Release)
The operation was canceled.
wasm_build
Canceling since a higher priority waiting request for wasm_build-2315 exists
pre_job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: fkirc/skip-duplicate-actions@v5. 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/
wasm_build (darwin, 64, Release)
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/setup-python@v5. 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/
wasm_build (linux, 64, Release)
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/setup-python@v5. 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/
wasm_build (windows, 64, Release)
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/setup-python@v5. 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/