Skip to content

fix: use shell-specific conda activation and check conda init status (Fixes #1313) #2129

fix: use shell-specific conda activation and check conda init status (Fixes #1313)

fix: use shell-specific conda activation and check conda init status (Fixes #1313) #2129

Re-run triggered March 18, 2026 23:00
Status Success
Total duration 3h 4m 59s
Artifacts 1

pr-check.yml

on: pull_request
Create VSIX
34s
Create VSIX
Matrix: TypeScript Unit Tests
Matrix: Smoke Tests
Matrix: E2E Tests
Matrix: Integration Tests (Multi-Root)
Matrix: Integration Tests
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Integration Tests (windows-latest, 3.12)
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/checkout@v4, actions/setup-node@v4, actions/setup-python@v5. 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/
Integration Tests (Multi-Root) (macos-latest, 3.10)
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/setup-python@v5. 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/