Skip to content

fix: handle cjs export assignment side effects #8086

fix: handle cjs export assignment side effects

fix: handle cjs export assignment side effects #8086

Triggered via pull request June 9, 2026 16:10
Status Success
Total duration 12m 20s
Artifacts 6

ci-diff.yml

on: pull_request
Build Bindings  /  ...  /  Build
7m 9s
Build Bindings / build / Build
Matrix: Build Bindings / test / test
Waiting for pending jobs
Build Bindings  /  ...  /  E2E Testing
Build Bindings / test / E2E Testing
Diff Benchmark Projects
4m 39s
Diff Benchmark Projects
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Build Bindings / build / Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, lynx-infra/cache/restore@5c6160a6a4c7fca80a2f3057bb9dfc9513fcb732, lynx-infra/upload-artifact@332ec52e99f7cbf1fbbdc9bcc09280d49147d092, rstackjs/rust-cache@8269079380bc35105b3ed8b0f1f7c9557c6dec93. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Diff Benchmark Projects
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: lynx-infra/download-artifact@79d9914484f933089c2840552cf439bac85debad. Actions will be forced to run with Node.js 24 by default starting June 16th, 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
bindings-x86_64-unknown-linux-gnu
110 MB
sha256:eab042b22f73ac202eae250198f96b836e6a47f187eac536b1e8ad88c036e2f1
rsdoctor-5298e9a5-ccaf6c4ceb
5.05 MB
sha256:daa8f29fb7bcfa5727ea3f97cbc7bcafa2dbe083a479804bcca503d336bb8af2
rsdoctor-56f2200b-ccaf6c4ceb
1.33 MB
sha256:3df8ffb85ed72cac4d7ba1572a77566457c3fb571602dabecf0a9059383f9eb4
rsdoctor-67752928-ccaf6c4ceb
2.86 MB
sha256:ec5a83bbe3879bfd84679891ccd6246324ace7cfd112e2773299e53c9345cb53
rsdoctor-b17c28eb-ccaf6c4ceb
1.15 MB
sha256:4713d7e1d06547ea235f0e555cedb3c982eaabfa4e4968be4d421b98df0ffabc
rsdoctor-d7f8788b-ccaf6c4ceb
4.96 MB
sha256:5da4d99c8ad0a7d5f4a856cb0db9ff209b4973dbc4995f31e062633d81fd56a1