🩹 [Patch]: Pester 6 test dependency packages correctly

[Marius Storhaug (MariusStorhaug)]

Publishing the module now preserves the intended Pester 6 compatibility range in its NuGet metadata, so release packaging no longer fails on an unsupported wildcard version bound.

Fixed: Pester 6 test dependency packaging

The module's test dependency accepts Pester versions from 6.0.0 through 6.999.999. This produces the NuGet constraint [6.0.0, 6.999.999] during release packaging.

Validation

• Invoke-Pester -Path .\tests\GoogleFonts.Tests.ps1 -Output Detailed (3 passed)

---

Technical details

• Replaced the wildcard upper bound in tests/GoogleFonts.Tests.ps1 with the concrete NuGet-serializable endpoint 6.999.999 while preserving the 6.0.0 minimum.
• Implementation plan progress: the single corrective step in 🪲 [Fix]: Package test dependency uses an invalid Pester 6 upper bound #275 is complete.

Changed surface	Standards checked	Framework docs checked	Result
tests/GoogleFonts.Tests.ps1	PowerShell module requirement syntax	Process-PSModule packaging configuration	Aligned

Relevant issues (or links)

-Fixes #275

[github-actions]

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]

Super-linter summary

Language	Validation result
CHECKOV	Pass ✅
GITHUB_ACTIONS	Pass ✅
GITHUB_ACTIONS_ZIZMOR	Pass ✅
GITLEAKS	Pass ✅
GIT_MERGE_CONFLICT_MARKERS	Pass ✅
JSON	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