v6.1.10

🩹 [Patch]: Action changes now trigger workflow validation and release checks (#401)

Workflow-only pull requests now behave correctly when the changed code lives in .github/actions, so action updates are validated and considered for release automation without manual workaround.

Changed: Workflow test pipelines now include action-code changes

The workflow test entry points now trigger on .github/actions/** changes in addition to workflow file changes, and action paths are treated as important artifacts in bump classification.

Changed: Release workflow now runs when action files change

The release workflow path filter now includes .github/actions/**, so action updates are not skipped by path-based gating.

Fixed: Repo-linter class-file exclusions are scoped to the processed repository

Super-linter exclusions are now expressed relative to the current repository working directory, which avoids path-handling issues in both default repository linting and test-repo linting scenarios.

Fixed: Root-module relative path rendering is path-API based

Root-module build comments now derive relative folder/file paths via System.IO.Path APIs instead of regex path replacement, which keeps region naming stable across path separators.

Technical Details

• Updated workflow path filters and important-file patterns in Workflow-Test-Default.yml, Workflow-Test-WithManifest.yml, and Release.yml.
• Added scoped FILTER_REGEX_EXCLUDE values in Linter.yml and Lint-Repository.yml.
• Reworked relative-path generation in Add-ContentFromItem.ps1 and Build-PSModuleRootModule.ps1 to use GetRelativePath, ChangeExtension, and separator-safe splitting.
• Added/updated class-fixture files under tests/srcTestRepo and tests/srcWithManifestTestRepo for loader/linter coverage.

Related issues

• PSModule/CurseForge#38
• PSModule/Template-PSModule#30
• PSModule/WoW#36