Skip to content

4. E2E tests VS Code Extension - Prisma CLI version 7.6.0-dev.4 #106

4. E2E tests VS Code Extension - Prisma CLI version 7.6.0-dev.4

4. E2E tests VS Code Extension - Prisma CLI version 7.6.0-dev.4 #106

Manually triggered March 17, 2026 15:07
Status Success
Total duration 2m 39s
Artifacts

4_e2e_tests.yml

on: workflow_dispatch
Matrix: E2E tests VS Code Extension
Trigger next workflow
9s
Trigger next workflow
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 4 warnings
E2E tests VS Code Extension (ubuntu-latest)
Option 'bundler' can only be used when 'module' is set to 'preserve' or to 'es2015' or later.
E2E tests VS Code Extension (macos-latest)
Option 'bundler' can only be used when 'module' is set to 'preserve' or to 'es2015' or later.
E2E tests VS Code Extension (windows-latest)
Option 'bundler' can only be used when 'module' is set to 'preserve' or to 'es2015' or later.
E2E tests VS Code Extension (ubuntu-latest)
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, coactions/setup-xvfb@v1. 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/
E2E tests VS Code Extension (macos-latest)
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, coactions/setup-xvfb@v1. 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/
E2E tests VS Code Extension (windows-latest)
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, coactions/setup-xvfb@v1. 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/
Trigger next workflow
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/