Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/sveltekit/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000

Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/node-core/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000

Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/node/vitest.junit.xml: Entity expansion limit exceeded: 1001 > 1000

Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/nextjs/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000

Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/core/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000

Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/replay-internal/vitest.junit.xml: Entity expansion limit exceeded: 1001 > 1000

Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/react/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000

Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/browser/vitest.junit.xml: Entity expansion limit exceeded: 1001 > 1000

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/download-artifact@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/

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/download-artifact@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/

Patch coverage defaulted to 100% because no changed files matched coverage data. Unmatched diff files: packages/core/src/utils/featureFlags.ts, packages/core/test/lib/utils/featureFlags.test.ts Sample coverage paths: ./mute.js, /Users/isaacs/dev/js/events-to-array/etoa.js, /home/runner/work/sentry-javascript/sentry-javascript/packages/browser/src/client.ts This usually indicates a path format mismatch between your coverage tool and the repository.

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/download-artifact@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/

Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov

No coverage files found

Please ensure your test framework is generating JUnit XML output.

No JUnit XML files found matching pattern: dev-packages/node-integration-tests/**/*.junit.xml