Skip to content

fix(core): Fix withStreamedSpan typing error add missing exports #45402

fix(core): Fix withStreamedSpan typing error add missing exports

fix(core): Fix withStreamedSpan typing error add missing exports #45402

Triggered via pull request April 8, 2026 15:39
Status Cancelled
Total duration 2m 54s
Artifacts

build.yml

on: pull_request
job_get_metadata  /  Get Metadata
10s
job_get_metadata / Get Metadata
Check lockfile
1m 58s
Check lockfile
Check file formatting
40s
Check file formatting
Check PR branches
5s
Check PR branches
Prepare E2E tests
0s
Prepare E2E tests
Matrix: job_browser_loader_tests
Matrix: job_browser_playwright_tests
Matrix: job_node_core_integration_tests
Matrix: job_node_integration_tests
Matrix: job_node_unit_tests
Matrix: job_remix_integration_tests
Size Check
0s
Size Check
Lint
0s
Lint
Circular Dependency Check
0s
Circular Dependency Check
Upload Artifacts
0s
Upload Artifacts
Browser Unit Tests
0s
Browser Unit Tests
Bun Unit Tests
0s
Bun Unit Tests
Deno Unit Tests
0s
Deno Unit Tests
Cloudflare Integration Tests
0s
Cloudflare Integration Tests
Node Overhead Check
0s
Node Overhead Check
Check for faulty .d.ts files
0s
Check for faulty .d.ts files
Matrix: job_e2e_tests
Matrix: job_optional_e2e_tests
All required jobs passed or were skipped
2s
All required jobs passed or were skipped
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 3 warnings
Build
Canceling since a higher priority waiting request for CI: Build & Test-lms/feat-span-streaming-exports exists
Build
The operation was canceled.
Check lockfile
Canceling since a higher priority waiting request for CI: Build & Test-lms/feat-span-streaming-exports exists
Check lockfile
The operation was canceled.
All required jobs passed or were skipped
Process completed with exit code 1.
CI: Build & Test
Canceling since a higher priority waiting request for CI: Build & Test-lms/feat-span-streaming-exports exists
job_get_metadata / Get Metadata
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@v3.0.1, mydea/pr-labels-action@fn/bump-node20. 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/
Check file formatting
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 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
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, dkhunt27/action-nx-affected-list@v6.1. 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/