🪲 [Fix]: Wildcard maximum versions no longer fail module processing

[Marius Storhaug (MariusStorhaug)]

Module requirements can now use wildcard maximum versions such as 1.* without module builds or installations failing. Versions remain constrained to the requested major or minor release line, while concrete maximum versions keep their existing behavior.

Fixed: wildcard maximum versions no longer fail module builds

Module manifests can now preserve wildcard maximum-version requirements instead of rejecting them as invalid version values. A requirement such as MaximumVersion = '1.*' remains usable during manifest generation.

Fixed: wildcard maximum versions resolve to the correct release range

Module installation translates wildcard maximum versions into an exclusive upper bound. For example, MinimumVersion = '1.0.0' and MaximumVersion = '1.*' resolve to the range [1.0.0,2.0.0), allowing 1.x releases without admitting 2.x releases. Unsupported wildcard patterns are reported clearly.

---

Technical details

• Manifest processing now keeps wildcard maximum versions as strings and only creates a numeric comparison bound for concrete versions.
• Installation version-spec conversion maps 1.* to the exclusive upper bound 2.0.0 and 1.2.* to 1.3.0; concrete maximum versions remain inclusive.
• Source test fixtures now exercise a ThreadJob requirement with ModuleVersion = '1.0.0' and MaximumVersion = '1.*'.
• The branch was synchronized with main; the repository's native Zensical workflow remains unchanged and continues to build directly from zensical.toml.
• Implementation plan progress: the scoped delivery bug in Build-PSModuleManifest fails when #Requires MaximumVersion uses wildcards #444 is completed by this pull request.

Changed surface	Standards checked	Framework docs checked	Result
.github/actions/** (PowerShell)	Naming, functions, action layout	Process-PSModule action conventions	Aligned
tests/** (PowerShell)	Pester fixture conventions	Module test repository layout	Aligned

Relevant issues (or links)

• FixesBuild-PSModuleManifest fails when #Requires MaximumVersion uses wildcards #444

[github-actions]

Super-linter summary

Language	Validation result
CHECKOV	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