Skip to content

Merge pull request #122 from GlobalHive/release-please--branches--mas… #86

Merge pull request #122 from GlobalHive/release-please--branches--mas…

Merge pull request #122 from GlobalHive/release-please--branches--mas… #86

Triggered via push March 17, 2026 16:51
Status Failure
Total duration 26s
Artifacts

ci.yml

on: push
Matrix: Test & Build
Lint & Format Check
21s
Lint & Format Check
Security Audit
15s
Security Audit
Publish Test Coverage
0s
Publish Test Coverage
Fit to window
Zoom out
Zoom in

Annotations

22 errors and 4 warnings
Security Audit
Process completed with exit code 1.
test/components/VTour.spec.ts > VTour Component - Comprehensive Test Suite > Backdrop Functionality > should show backdrop when global backdrop prop is true: test/components/VTour.spec.ts#L580
AssertionError: expected null to be truthy - Expected: true + Received: null ❯ test/components/VTour.spec.ts:580:24
test/components/VTour.spec.ts > VTour Component - Comprehensive Test Suite > should remove old highlight and apply new scoped highlight after hot-switch name change: test/components/VTour.spec.ts#L555
AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ test/components/VTour.spec.ts:555:58
test/components/VTour.spec.ts > VTour Component - Comprehensive Test Suite > Highlight Functionality > should remove highlight when stopping tour: test/components/VTour.spec.ts#L515
AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ test/components/VTour.spec.ts:515:65
test/components/VTour.spec.ts > VTour Component - Comprehensive Test Suite > Highlight Functionality > should handle highlight functionality: test/components/VTour.spec.ts#L493
AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ test/components/VTour.spec.ts:493:66
test/components/VTour.spec.ts > VTour Component - Comprehensive Test Suite > Tour Navigation and Control > should stop tour correctly: test/components/VTour.spec.ts#L330
AssertionError: expected undefined to be truthy - Expected: true + Received: undefined ❯ test/components/VTour.spec.ts:330:53
test/components/VTour.spec.ts > VTour Component - Comprehensive Test Suite > Basic Component Properties > should handle backdrop prop: test/components/VTour.spec.ts#L132
AssertionError: expected null to be truthy - Expected: true + Received: null ❯ test/components/VTour.spec.ts:132:55
test/components/VTour.spec.ts > VTour Component - Comprehensive Test Suite > Basic Component Properties > should accept custom button labels: test/components/VTour.spec.ts#L117
AssertionError: the given combination of arguments (undefined and string) is invalid for this assertion. You can use an array, a map, an object, a set, a string, or a weakset instead of a string ❯ test/components/VTour.spec.ts:117:43
test/components/VTour.spec.ts > VTour Component - Comprehensive Test Suite > Basic Component Properties > should render with default props: test/components/VTour.spec.ts#L94
AssertionError: expected null to be truthy - Expected: true + Received: null ❯ test/components/VTour.spec.ts:94:55
Test & Build (22)
The strategy configuration was canceled because "test._20" failed
test/components/VTour.spec.ts > VTour Component - Comprehensive Test Suite > Backdrop Functionality > should show backdrop when global backdrop prop is true: test/components/VTour.spec.ts#L580
AssertionError: expected null to be truthy - Expected: true + Received: null ❯ test/components/VTour.spec.ts:580:24
test/components/VTour.spec.ts > VTour Component - Comprehensive Test Suite > should remove old highlight and apply new scoped highlight after hot-switch name change: test/components/VTour.spec.ts#L555
AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ test/components/VTour.spec.ts:555:58
test/components/VTour.spec.ts > VTour Component - Comprehensive Test Suite > Highlight Functionality > should remove highlight when stopping tour: test/components/VTour.spec.ts#L515
AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ test/components/VTour.spec.ts:515:65
test/components/VTour.spec.ts > VTour Component - Comprehensive Test Suite > Highlight Functionality > should handle highlight functionality: test/components/VTour.spec.ts#L493
AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ test/components/VTour.spec.ts:493:66
test/components/VTour.spec.ts > VTour Component - Comprehensive Test Suite > Tour Navigation and Control > should stop tour correctly: test/components/VTour.spec.ts#L330
AssertionError: expected undefined to be truthy - Expected: true + Received: undefined ❯ test/components/VTour.spec.ts:330:53
test/components/VTour.spec.ts > VTour Component - Comprehensive Test Suite > Basic Component Properties > should handle backdrop prop: test/components/VTour.spec.ts#L132
AssertionError: expected null to be truthy - Expected: true + Received: null ❯ test/components/VTour.spec.ts:132:55
test/components/VTour.spec.ts > VTour Component - Comprehensive Test Suite > Basic Component Properties > should accept custom button labels: test/components/VTour.spec.ts#L117
AssertionError: the given combination of arguments (undefined and string) is invalid for this assertion. You can use an array, a map, an object, a set, a string, or a weakset instead of a string ❯ test/components/VTour.spec.ts:117:43
test/components/VTour.spec.ts > VTour Component - Comprehensive Test Suite > Basic Component Properties > should render with default props: test/components/VTour.spec.ts#L94
AssertionError: expected null to be truthy - Expected: true + Received: null ❯ test/components/VTour.spec.ts:94:55
Security Audit
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-node@v4. 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/
Test & Build (20)
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-node@v4. 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/
Lint & Format Check
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-node@v4. 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/
Test & Build (22)
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-node@v4. 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/