Content-Length: 366045 | pFad | http://github.com/PowerShell/PowerShell/pull/25531

46 Verify Pester 4 usage and unload Pester 5 if present by JustinGrote · Pull Request #25531 · PowerShell/PowerShell · GitHub
Skip to content

Verify Pester 4 usage and unload Pester 5 if present #25531

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

JustinGrote
Copy link
Contributor

Ensure that Pester 4 is used for testing, while unloading Pester 5 if it is currently loaded. This helps avoid confusing error messages for users who have Pester 5 installed.

@JustinGrote JustinGrote requested review from jshigetomi and a team as code owners May 9, 2025 19:26
Copy link
Collaborator

@iSazonov iSazonov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are too many unrelated changes, which complicates the review. Could you please delete them?

@JustinGrote
Copy link
Contributor Author

@iSazonov sorry, the Powershell vscode formatter went nuts and I didn't mean to commit. I'll fix, stand by.

Copy link
Contributor Author

@JustinGrote JustinGrote left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

@iSazonov iSazonov added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label May 10, 2025
@JustinGrote JustinGrote requested a review from iSazonov May 16, 2025 02:21
@JustinGrote
Copy link
Contributor Author

@iSazonov looks like it needs a re-review after a tag add for some reason.

@iSazonov
Copy link
Collaborator

/azp run PowerShell-CI-linux-packaging,PowerShell-Windows-Packaging-CI

Copy link

Azure Pipelines successfully started running 2 pipeline(s).

@JustinGrote JustinGrote requested a review from iSazonov May 17, 2025 16:00
@JustinGrote
Copy link
Contributor Author

This one is still stuck. I think it needs @TravisEz13 or @jshigetomi approval
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants








ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://github.com/PowerShell/PowerShell/pull/25531

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy