Skip to content

Conversation

guhetier
Copy link
Contributor

Description

It is easy to miss / forget about the powershell 7 requirement for running scripts, especially when Windows still ship with version 5.
This makes the script failure clearly indicate that the powershell version is the reason for the failures (versus the current undefined variables errors).

Resolves #4810

Testing

CI

Documentation

N/A

Copy link

codecov bot commented Feb 12, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.03%. Comparing base (ba795e0) to head (9e4b57a).
Report is 30 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4811      +/-   ##
==========================================
- Coverage   87.38%   87.03%   -0.36%     
==========================================
  Files          56       56              
  Lines       17400    17425      +25     
==========================================
- Hits        15205    15165      -40     
- Misses       2195     2260      +65     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@guhetier guhetier marked this pull request as ready for review February 13, 2025 22:17
@guhetier guhetier requested a review from a team as a code owner February 13, 2025 22:17
@nibanks nibanks merged commit 35c3433 into main Feb 14, 2025
398 of 399 checks passed
@nibanks nibanks deleted the pwsh_version branch February 14, 2025 11:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Configuration, build and test Powershell scripts fail on older powershell with a confusing error
2 participants