Context

In the current Process-PSModule workflow, version numbers are generated during the Publish step. This means the artifact that is tested may not be identical to the artifact that is published, since the version is stamped after testing.

Request

Version generation should be moved from the Publish step to the Build step. This ensures the artifact is fully versioned before testing, so what gets tested is exactly what gets published. Additionally, having a versioned prerelease artifact available after build enables sharing it with other workflows (e.g., PSModule/GitHub-Script action tests).

What is expected

• The Build step produces a fully versioned module artifact (including prerelease tags if applicable)
• The Test step tests the exact versioned artifact
• The Publish step publishes the same unaltered artifact
• Prerelease artifacts are available for downstream consumption after the build step

Acceptance criteria

• Version number is determined and applied during the Build step
• The tested artifact is byte-identical to the published artifact
• Prerelease artifacts can be consumed by other workflows

Technical decisions

To be determined during implementation planning — evaluate how version information is currently generated and where it gets stamped into the manifest.

Implementation plan

• Identify where version generation currently occurs in the Publish step
• Move version calculation logic to the Build step
• Apply the version to the module manifest during build
• Ensure the Test step uses the versioned artifact
• Ensure the Publish step publishes without modifying the artifact
• Make the prerelease artifact available for downstream workflows
• Test the full build → test → publish pipeline with the new ordering