Bump PSModule/Invoke-Pester from 4.2.4 to 5.1.0#27
Merged
Marius Storhaug (MariusStorhaug) merged 1 commit intoJul 9, 2026
Merged
Conversation
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Updates the CI test workflow (Action-Test.yml) to the latest Invoke-Pester release. This supersedes the original 4.2.4 -> 4.2.5 bump. The v5.0.0 breaking change (Version/Prerelease inputs now control Pester and must be renamed to GitHubVersion/GitHubPrerelease) does not affect this workflow, because the Invoke-Pester step sets no Version/Prerelease inputs. Invoke-Pester is used only in the test workflow, so this has no runtime impact on consumers of the action.
Marius Storhaug (MariusStorhaug)
force-pushed
the
dependabot/github_actions/PSModule/Invoke-Pester-4.2.5
branch
from
01f6172 to
77476dc
Compare
Marius Storhaug (MariusStorhaug)
changed the title
Copilot started reviewing on behalf of
Marius Storhaug (MariusStorhaug)
July 9, 2026 22:32
View session
There was a problem hiding this comment.
Pull request overview
Updates the GitHub Actions CI workflow to use the latest PSModule/Invoke-Pester action release (v5.1.0), keeping the repository’s test runner up to date without impacting the published action’s runtime behavior (since this dependency is only used in CI).
Changes:
- Bump
PSModule/Invoke-Pesterfrom v4.2.4 to v5.1.0 in theAction-Test.ymlworkflow. - Keep the action pinned to a specific commit SHA while updating the corresponding version comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Marius Storhaug (MariusStorhaug)
deleted the
dependabot/github_actions/PSModule/Invoke-Pester-4.2.5
branch
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps PSModule/Invoke-Pester from 4.2.4 to 5.1.0 — the latest release.
This updates the original Dependabot PR (which targeted 4.2.5) straight to the current latest, since 4.2.5/4.2.6 and the 5.x line were all released while this PR sat open (auto-rebase was disabled after 30 days). Invoke-Pester is used only in the
Action-Test.ymlCI test workflow, so this change has no runtime impact on consumers of this action.Major version note (v5.0.0)
The 5.0.0 release contains one breaking change: the
VersionandPrereleaseinputs now control the Pester version instead of the internal GitHub bootstrap module, which moved toGitHubVersion/GitHubPrerelease. This workflow's Invoke-Pester step sets neitherVersionnorPrerelease(onlyenv: data), so the breaking change does not apply. With noVersioninput, v5.x installs the latest available Pester by default — the per-repository#Requiresdeclaration in the test files remains the safety net (see #32, which locks tests to Pester 6.x).v5.x highlights
Version/Prereleasenow select the Pester version (NuGet range syntax); GitHub bootstrap controls renamed toGitHubVersion/GitHubPrerelease; the loaded Pester version now matches the resolved version and is reported accurately.Guidinput to pin Pester by module identity (validated at install time). Additive, no impact here.Pinned by commit SHA per repository convention:
4ff33199141fdf22568990b6107fe3148ae93a1c # v5.1.0.