🪲 [Fix]: Built modules with resolved versions can be tested#119
Merged
Marius Storhaug (MariusStorhaug) merged 5 commits intoJul 8, 2026
Merged
Conversation
…ersion Install-PSModuleHelpers now installs the built module into a folder matching the manifest ModuleVersion instead of the 999.0.0 placeholder, which is required now that the build pipeline stamps the real version (PSModule/Process-PSModule#326). Temporarily pinned to the fix branch (PSModule/Install-PSModuleHelpers#19); will repin to the released tag before merge.
Copilot started reviewing on behalf of
Marius Storhaug (MariusStorhaug)
July 8, 2026 01:21
View session
There was a problem hiding this comment.
Pull request overview
Updates the Test-PSModule composite action to install Install-PSModuleHelpers from a revision that installs built modules into a version folder matching the manifest ModuleVersion, avoiding Import-Module failures now that builds stamp the real resolved version.
Changes:
- Bump
PSModule/Install-PSModuleHelpersfromv1.0.7to a temporary fix-branch commit SHA that installs modules at their real versioned path.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Copilot started reviewing on behalf of
Marius Storhaug (MariusStorhaug)
July 8, 2026 01:26
View session
Copilot started reviewing on behalf of
Marius Storhaug (MariusStorhaug)
July 8, 2026 12:10
View session
Marius Storhaug (MariusStorhaug)
changed the title
Copilot started reviewing on behalf of
Marius Storhaug (MariusStorhaug)
July 8, 2026 12:20
View session
Marius Storhaug (MariusStorhaug)
added a commit
that referenced
this pull request
Jul 8, 2026
Bumps [PSModule/Invoke-Pester](https://github.com/PSModule/Invoke-Pester) from **v4.2.4** to **v4.2.6** (latest). Supersedes #115, which only bumped to v4.2.5 — going straight to the latest avoids chaining two dependency PRs. ## What this PR changes A single pin in [action.yml](action.yml): ``` uses: PSModule/Invoke-Pester@9cf262a # v4.2.6 ``` Upstream changes inside Invoke-Pester between v4.2.4 and v4.2.6 are captured in its own [release notes](https://github.com/PSModule/Invoke-Pester/releases). Those (e.g. its internal upload-artifact / GitHub-Script bumps) are internal to the Invoke-Pester action, not separate dependencies of this repo. ## Status of all pinned actions in this repo | Action | Pinned | Latest | Status | | --- | --- | --- | --- | | `actions/checkout` | v7.0.0 | v7.0.0 | up to date | | `super-linter/super-linter` | v8.7.0 | v8.7.0 | up to date | | `PSModule/Release-GHRepository` | v2.0.2 | v2.0.2 | up to date | | `PSModule/Invoke-Pester` | v4.2.6 | v4.2.6 | **this PR** | | `PSModule/Install-PSModuleHelpers` | v1.0.7 | v1.0.8 | handled by #119 |
…dulehelpers # Conflicts: # action.yml
Copilot started reviewing on behalf of
Marius Storhaug (MariusStorhaug)
July 8, 2026 15:13
View session
Copilot started reviewing on behalf of
Marius Storhaug (MariusStorhaug)
July 8, 2026 15:26
View session
Marius Storhaug (MariusStorhaug)
deleted the
fix/bump-install-psmodulehelpers
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.
Built modules whose manifests carry a real, resolved version can now be tested by
Test-PSModule. Previously the action installed the built module under the historical999.0.0placeholder folder, so module tests failed once the build flow started stamping manifests with the version that will actually be shipped.Fixed: Built modules with resolved versions can be tested
Test-PSModulenow installs and validates built module outputs whose manifestModuleVersionhas already been resolved to the real build version. The module is installed under a matching version folder before module tests run, so PowerShell accepts the manifest and Pester validates the artifact from the expected path.This is delivered by bumping the pinned
PSModule/Install-PSModuleHelperstov1.0.8, which installs built modules at their real version instead of the999.0.0placeholder.Technical Details
action.yml:PSModule/Install-PSModuleHelperspin bumpedv1.0.7->v1.0.8(the release from PSModule/Install-PSModuleHelpers#19).src/tests/Module/PSModule/PSModule.Tests.ps1: new test asserting the installed version folder matches the manifestModuleVersion, guarding against a regression to the999.0.0behavior.tests/outputTestRepo/outputs/module/PSModuleTest/PSModuleTest.psd1: fixtureModuleVersionupdated999.0.0->3.0.11to model the current build output.main, which already carries theactions/checkoutv7.0.0,super-linterv8.7.0, andPSModule/Invoke-Pesterv4.2.6 pins, so this PR no longer changes those.