Skip to content

Rewrite nested JSX component paths to direct hoisted exports #10030

Rewrite nested JSX component paths to direct hoisted exports

Rewrite nested JSX component paths to direct hoisted exports #10030

Triggered via pull request April 24, 2026 19:56
Status Cancelled
Total duration 3m 51s
Artifacts

ci.yml

on: pull_request
Matrix: build-compiler
test-devcontainer
3m 22s
test-devcontainer
pkg-pr-new
0s
pkg-pr-new
api-docs
0s
api-docs
Matrix: test-installation-npm
Matrix: test-installation-pnpm
Matrix: test-integration-rewatch
publish
publish
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 3 warnings
test-devcontainer
Canceling since a higher priority waiting request for ci-refs/pull/8293/merge-1 exists
test-devcontainer
The operation was canceled.
build-compiler (windows-2025, 5.3.0, true, win32-x64, x86_64-pc-windows-gnu, .exe, release)
Canceling since a higher priority waiting request for ci-refs/pull/8293/merge-1 exists
build-compiler (ubuntu-24.04-arm, ocaml-variants.5.3.0+options,ocaml-option-static, true, true, t...
Canceling since a higher priority waiting request for ci-refs/pull/8293/merge-1 exists
build-compiler (ubuntu-24.04, ocaml-variants.5.3.0+options,ocaml-option-static, true, true, linux...
Canceling since a higher priority waiting request for ci-refs/pull/8293/merge-1 exists
build-compiler (ubuntu-24.04, ocaml-variants.5.0.0+options,ocaml-option-static, linux-x64, x86_64...
Canceling since a higher priority waiting request for ci-refs/pull/8293/merge-1 exists
build-compiler (macos-15-intel, 5.3.0, true, darwin-x64, x86_64-apple-darwin, release)
Canceling since a higher priority waiting request for ci-refs/pull/8293/merge-1 exists
CI
Canceling since a higher priority waiting request for ci-refs/pull/8293/merge-1 exists
build-compiler (ubuntu-24.04-arm, ocaml-variants.5.3.0+options,ocaml-option-static, true, true, t...
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 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-compiler (ubuntu-24.04, ocaml-variants.5.3.0+options,ocaml-option-static, true, true, 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 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-compiler (ubuntu-24.04, ocaml-variants.5.0.0+options,ocaml-option-static, linux-x64, x86_64...
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 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/