fix: restore Windows PowerShell 5.1 import compatibility #116
Workflow file for this run
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| name: Test | |
| permissions: | |
| contents: read | |
| checks: write | |
| pull-requests: write | |
| issues: write | |
| on: | |
| push: | |
| branches: [ main ] | |
| pull_request: | |
| workflow_dispatch: | |
| jobs: | |
| # Delegate to the psake org's shared module CI workflow. It runs the full build/test suite | |
| # (Build + Analyze + Pester) on PowerShell 7+ across Linux/Windows/macOS and on the real | |
| # Windows PowerShell 5.1 (Desktop) engine, so regressions like the 0.8.0 ternary that broke | |
| # module import on 5.1 are caught by the standard test run rather than a separate smoke test. | |
| ci: | |
| name: CI | |
| # TODO: pin to a tagged release or commit SHA of psake/.github once the 5.1 (test_powershell) | |
| # job has merged there. Until then `@main` is required so this resolves to a version that | |
| # includes the Windows PowerShell 5.1 job. | |
| uses: psake/.github/.github/workflows/ModuleCI.yml@main |