Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
Pins the Pester version required for the module to
4.10.1
sinceRequiredModules
doesn't appear to support aMaximumVersion
, and also pins the build pipeline to maximum version of4.99.99
for Pester.Context
Currently users can install Pester v5 and PSKoans will be trying to utilise that version on import; this will cause things to break.
This should force PowerShellGet to retrieve the right version from the gallery when installing the new PSKoans version and avoid that breakage until I can update this module to work with v5 of Pester.
Changes
RequiredVersion
in the manifest for Pester-MaximumVersion
in the CI pipeline for PesterChecklist