v3.0.13
🪲 [Fix]: Built modules with resolved versions can be tested (#119)
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 historical 999.0.0 placeholder 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-PSModule now installs and validates built module outputs whose manifest ModuleVersion has 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-PSModuleHelpers to v1.0.8, which installs built modules at their real version instead of the 999.0.0 placeholder.
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.- The branch is merged up to date with
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.