You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maintain the module's automation on the current PSModule/Process-PSModule release so builds, tests, publication, and documentation follow the supported pipeline contract.
Acceptance criteria
.github/workflows/Process-PSModule.yml pins the reusable workflow to the immutable commit for v6.1.19.
The caller continues to map only the required APIKey secret explicitly.
Documentation builds use the Zensical configuration expected by Process-PSModule v6.1.13 and later; the obsolete MkDocs configuration is removed.
The migrated configuration follows the current PSModule/Template-PSModule convention and retains the module documentation site's name, repository links, icons, navigation, search, markdown extensions, and social links.
YAML and TOML configuration validation succeeds.
Constraints and non-goals
Pin the reusable workflow to its release commit SHA rather than a mutable tag.
Do not change module source, public behavior, or publishing credentials.
Update .github/workflows/Process-PSModule.yml to bf67cd90269ca5ce25cd76b203678907dc2984b4 (v6.1.19).
Preserve the existing APIKey: ${{ secrets.APIKey }} mapping; the workflow contract requires it and GitHub secret names are case-insensitive.
Replace .github/mkdocs.yml with .github/zensical.toml based on the current PSModule/Template-PSModule configuration, preserving the repository's templated values.
Validate the changed YAML with yamllint and parse the TOML configuration using PowerShell before opening the draft pull request.
Implementation plan
Verify the v6.1.19 caller contract and the repository's current configuration.
Validate the existing YAML and prepare the Zensical configuration migration.
Update the workflow pin and replace the legacy documentation configuration.
Validate the changed YAML and TOML configuration.
Create and push a micro commit, then open a draft delivery pull request.
Context and request
Maintain the module's automation on the current
PSModule/Process-PSModulerelease so builds, tests, publication, and documentation follow the supported pipeline contract.Acceptance criteria
.github/workflows/Process-PSModule.ymlpins the reusable workflow to the immutable commit forv6.1.19.APIKeysecret explicitly.PSModule/Template-PSModuleconvention and retains the module documentation site's name, repository links, icons, navigation, search, markdown extensions, and social links.Constraints and non-goals
Technical decisions
.github/workflows/Process-PSModule.ymltobf67cd90269ca5ce25cd76b203678907dc2984b4(v6.1.19).APIKey: ${{ secrets.APIKey }}mapping; the workflow contract requires it and GitHub secret names are case-insensitive..github/mkdocs.ymlwith.github/zensical.tomlbased on the currentPSModule/Template-PSModuleconfiguration, preserving the repository's templated values.yamllintand parse the TOML configuration using PowerShell before opening the draft pull request.Implementation plan