PSModule v5

[MariusStorhaug]

In this release

Bumps the Process-PSModule workflow from v4 to v5, now being possible to "host" all the workflows in a single workflow. This makes you able to move away from the linter.yml and the Nightly-Run.yml, and instead just host everything from the one Process-PSModule.yml workflow.

Workflow consolidation and scheduling

• Updated the reusable workflow version in .github/workflows/Process-PSModule.yml from v4 to v5 for PSModule/Process-PSModule/.github/workflows/workflow.yml, ensuring we use the latest improvements and fixes.
• Updated workflow to trigger on both nightly schedule, manual dispatch, and pull requests to main, ensuring all use cases are covered in one workflow.
• Removed the separate .github/workflows/Nightly-Run.yml workflow and merged its nightly schedule and manual trigger into .github/workflows/Process-PSModule.yml to streamline job management.
• Added dependencies and github-actions labels to Dependabot updates for GitHub Actions, making it easier to identify and filter these PR, also it will no longer collide with version labels.
• Removed the .github/workflows/Linter.yml file, which previously ran the Super-Linter on pull requests, likely to reduce redundancy or because linting is now handled in the Process-PSModule.

QnA

• Q: Can I still have the different workflows in my own repo.
• A: Yes, you can. You will also soon get settings that will allow you to configure the linter inside the workflow. You can also still bump the version of your nightly runs to v5 and have that on a schedule and manual runs. These do not have to be in a single workflow.

[github-actions]

Module Template-PSModule - 0.0.3 published to the PowerShell Gallery.

[github-actions]

GitHub release for Template-PSModule v0.0.3 has been created.