🪲 [Fix]: Restore correct release versioning in the publish pipeline#363
Merged
Marius Storhaug (MariusStorhaug) merged 4 commits intoJul 7, 2026
Merged
Conversation
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
Copilot started reviewing on behalf of
Marius Storhaug (MariusStorhaug)
July 7, 2026 22:53
View session
Contributor
There was a problem hiding this comment.
Pull request overview
This PR restores correct module release versioning in the publish pipeline by reverting the PSModule/Publish-PSModule action pin to a version that performs version calculation/stamping at publish time, and updates Dependabot to avoid reintroducing premature major upgrades of first-party lifecycle actions.
Changes:
- Revert
PSModule/Publish-PSModulepin fromv3.0.0back tov2.2.4in the publish workflow. - Configure Dependabot to ignore semver-major updates for
PSModule/*-PSModuleGitHub Actions dependencies.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| .github/workflows/Publish-Module.yml | Re-pins PSModule/Publish-PSModule to v2.2.4 to restore version calculation/stamping at publish time. |
| .github/dependabot.yml | Adds an ignore rule to prevent Dependabot from proposing major bumps for PSModule/*-PSModule actions. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Copilot started reviewing on behalf of
Marius Storhaug (MariusStorhaug)
July 7, 2026 23:00
View session
Marius Storhaug (MariusStorhaug)
deleted the
fix/326-contain-publish-v3-regression
branch
Marius Storhaug (MariusStorhaug)
added a commit
that referenced
this pull request
Jul 8, 2026
- Resolve Get-Settings.yml modify/delete conflict (keep deletion; replaced by Plan.yml) - Keep publish-only Publish-Module.yml (Publish-PSModule v3.0.0) over main's #363 revert - Bump Resolve-PSModuleVersion pin v1.0.1 -> v1.1.0 (#348 always-emit fix) - Align Plan.yml checkout to v7.0.0 (matches main)
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.
The module publishing pipeline once again calculates and stamps the real release version before publishing, so consumer releases are versioned and tagged correctly instead of shipping the build-time placeholder. This reverts the premature
Publish-PSModulemajor upgrade that leftmainin an inconsistent state.Fixed: Releases are versioned correctly again
Publish-PSModuleis pinned back tov2.2.4, which calculates the release version (from labels and tags) and stamps it into the module manifest at publish time. Onmain,Build-PSModule(v4) only stamps a999.0.0placeholder and does not compute the real version, andPublish-PSModulev3.0.0 is publish-only — it expects the manifest to already carry the final version. With v3.0.0 in place, nothing in the pipeline computed the real version, so a real consumer release would have published and tagged999.0.0. Reverting tov2.2.4restores the fully consistent old pipeline: Get-Settings → Build (v4,999.0.0) → Publish (v2.2.4, calculates + stamps).Only the
Publish-PSModulepin is reverted. The other action bumps from #358 (actions/checkoutv7.0.0,super-linterv8.7.0) are left in place.Technical Details
.github/workflows/Publish-Module.yml:PSModule/Publish-PSModulepin reverted03c0f8b… # v3.0.0→8917aed… # v2.2.4. This is the exact pin [Patch]: Update GitHub Actions dependencies to latest pinned versions #358 replaced; nowith:inputs changed — v2.2.4 consumes the version-calculation inputs the workflow already passes, whereas v3.0.0 silently ignored them..github/workflows/Publish-Module.yml: normalized theAPIKeyaction input fromsecrets.APIKEYtosecrets.APIKeyto match theAPIKeysecret declaration and the other workflows (workflow.yml,Workflow-Test-*.yml). GitHub Actions secret names are case-insensitive, so this is a consistency-only change with no behavioral effect (flagged during Copilot review).Resolve-PSModuleVersionwith the Resolve-PSModuleVersion: Always emit a version regardless of publish decision #348 fix, then rebase and land PR 🚀 [Feature]: Plan job decides version before build so tested artifact equals published artifact #342 (Plan job + Build v5 + publish-only Publish) and re-pin the first-party actions together.