⬆️ [Dependency]: Update Process-PSModule to v6.1.17 - #54
Open
Marius Storhaug (MariusStorhaug) wants to merge 1 commit into
Open
⬆️ [Dependency]: Update Process-PSModule to v6.1.17#54Marius Storhaug (MariusStorhaug) wants to merge 1 commit into
Marius Storhaug (MariusStorhaug) wants to merge 1 commit into
Conversation
v6.1.16 restores the configured VersionPrefix on release tags, which PSSemVer needs before its next release: v1.1.10 published from v6.1.15 was tagged 1.1.10 instead of v1.1.11's expected v prefix. v6.1.17 additionally fixes wildcard MaximumVersion handling, the '6.*' form this repo's test suite declares. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
No Significant Changes DetectedThis PR does not contain changes to files that would trigger a new release:
Build, test, and publish stages will be skipped for this PR. If you believe this is incorrect, please verify that your changes are in the correct locations. |
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
Marius Storhaug (MariusStorhaug)
marked this pull request as ready for review
August 8, 2026 16:13
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.
PSSemVer moves onto Process-PSModule v6.1.17, which restores the version prefix on release tags before the next release goes out.
Fixed: The next release is tagged
v1.1.11, not1.1.11PSSemVer was pinned to v6.1.15, which derives the release tag from the compiled manifest's
ModuleVersion. That value isMajor.Minor.Patchby definition and cannot carry the configuredVersionPrefix, so the prefix was dropped. This repository's own v1.1.10 release is the evidence: every tag before it isv1.1.x, and it published as1.1.10.v6.1.16 fixes that, so the next release tags as
v1.1.11and the history is continuous again. The published1.1.10tag is deliberately left alone — the release and its attached artifact are public and the PowerShell Gallery listing links to it.Fixed: Wildcard maximum versions no longer fail module processing
v6.1.17 fixes handling of wildcard maximum versions such as
1.*. This repository declares exactly that form intests/PSSemVer.Tests.ps1:#Requires -Modules @{ ModuleName = 'Pester'; ModuleVersion = '6.0.0'; MaximumVersion = '6.*' }Technical Details
.github/workflows/Process-PSModule.yml:@688896d # v6.1.15->@169c576 # v6.1.17.github-actionsecosystem is configured with a 7-day cooldown, so v6.1.16 would not be offered until 2026-08-10 and v6.1.17 later still — both after the next release would have been mis-tagged.Related issues