Skip to content

⬆️ [Dependency]: Update Process-PSModule to v6.1.17 - #54

Open
Marius Storhaug (MariusStorhaug) wants to merge 1 commit into
mainfrom
bump-process-psmodule-to-v6-1-17
Open

⬆️ [Dependency]: Update Process-PSModule to v6.1.17#54
Marius Storhaug (MariusStorhaug) wants to merge 1 commit into
mainfrom
bump-process-psmodule-to-v6-1-17

Conversation

@MariusStorhaug

Copy link
Copy Markdown
Member

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, not 1.1.11

PSSemVer was pinned to v6.1.15, which derives the release tag from the compiled manifest's ModuleVersion. That value is Major.Minor.Patch by definition and cannot carry the configured VersionPrefix, so the prefix was dropped. This repository's own v1.1.10 release is the evidence: every tag before it is v1.1.x, and it published as 1.1.10.

v6.1.16 fixes that, so the next release tags as v1.1.11 and the history is continuous again. The published 1.1.10 tag 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 in tests/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.
  • Bumped ahead of Dependabot rather than waiting for it. The github-actions ecosystem 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

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>
@github-actions

github-actions Bot commented Aug 8, 2026

Copy link
Copy Markdown

No Significant Changes Detected

This PR does not contain changes to files that would trigger a new release:

Pattern Description
^src/ Matches files where path matches this pattern
^README\.md$ Matches files where path matches this pattern

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.

@github-actions

github-actions Bot commented Aug 8, 2026

Copy link
Copy Markdown

Super-linter summary

Language Validation result
CHECKOV Pass ✅
GITHUB_ACTIONS Pass ✅
GITLEAKS Pass ✅
GIT_MERGE_CONFLICT_MARKERS Pass ✅
MARKDOWN Pass ✅
NATURAL_LANGUAGE Pass ✅
POWERSHELL Pass ✅
PRE_COMMIT Pass ✅
SPELL_CODESPELL Pass ✅
TRIVY Pass ✅
YAML Pass ✅

All files and directories linted successfully

For more information, see the GitHub Actions workflow run

Powered by Super-linter

@MariusStorhaug
Marius Storhaug (MariusStorhaug) marked this pull request as ready for review August 8, 2026 16:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Patch Fixes bugs or adds small fixes to existing functionality

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Restore the configured VersionPrefix on release tags created by Publish-PSModule

1 participant