Bump PSModule/Process-PSModule/.github/workflows/workflow.yml from 5.4.3 to 5.5.7#23
Open
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [PSModule/Process-PSModule/.github/workflows/workflow.yml](https://github.com/psmodule/process-psmodule) from 5.4.3 to 5.5.7. - [Release notes](https://github.com/psmodule/process-psmodule/releases) - [Commits](PSModule/Process-PSModule@60bdf8a...ce64918) --- updated-dependencies: - dependency-name: PSModule/Process-PSModule/.github/workflows/workflow.yml dependency-version: 5.5.7 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
No Significant Changes DetectedThis PR does not contain changes to files that would trigger a new release:
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. |
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
Marius Storhaug (MariusStorhaug)
added a commit
that referenced
this pull request
Jul 10, 2026
…a (secret + variable) in tests (#26) Updates the shared `Process-PSModule` reusable workflow from `v5.4.3` to the latest `v6.1.1`, and adds a worked example of the v6 `TestData` feature so module authors can see how to pass a secret and a variable down to their tests. ## Changed: Process-PSModule bumped to v6.1.1 The template now consumes `Process-PSModule` `v6.1.1` (was `v5.4.3`). The v6 major release replaced the fixed `TEST_*` workflow secret inputs with a single `TestData` object; the template did not use any `TEST_*` secrets, and the `.github/PSModule.yml` settings keys used here (`Test.CodeCoverage.PercentTarget`, `Linter.env`) remain valid in v6. ## New: Showcase for passing test data to the module tests `.github/workflows/Process-PSModule.yml` now passes a `TestData` object with one secret and one variable: ```yaml TestData: >- { "secrets": { "TEST_SECRET": "${{ secrets.TEST_SECRET }}" }, "variables": { "TEST_VARIABLE": ${{ toJSON(vars.TEST_VARIABLE) }} } } ``` - Entries in `secrets` are masked in the logs; entries in `variables` are not. - Both are exposed to the module test jobs as `$env:<name>`. `tests/Environment.Tests.ps1` consumes them and asserts they arrive. The tests **skip** when the values are absent, so a fresh repository created from this template stays green (GitHub does not copy repository secrets/variables to template instances). ## Technical Details - `.github/workflows/Process-PSModule.yml`: pin `workflow.yml@60bdf8a…` (`v5.4.3`) → `@ea19a3eb1293246d1b00e4faae1544442c3be0ec` (`v6.1.1`); add the commented `TestData` block. - `tests/Environment.Tests.ps1`: new, mirrors the sibling test-file header; `-Skip` when the env var is empty; PSScriptAnalyzer-clean against `.github/linters/.powershell-psscriptanalyzer.psd1`. - Non-sensitive demo repository secret `TEST_SECRET` and variable `TEST_VARIABLE` were added to this repo so its own CI exercises the showcase; both are safe placeholder values. - Validated locally with Pester: 2 passed with the env vars set, 2 skipped without. PR checks (pull_request event) are green. - Supersedes Dependabot PR #23 (bump to `5.5.7`), which Dependabot will close automatically once this merges to a higher version. ### Known limitation on v6.1.1 On v6.1.0/v6.1.1 the `Plan` job fails on `schedule` and `workflow_dispatch` events (its `Resolve-Version` step requires a `pull_request` event), so the template's scheduled/manual runs will fail until fixed upstream. `pull_request` runs — the primary development path — are unaffected. Tracked in PSModule/Process-PSModule#373.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps PSModule/Process-PSModule/.github/workflows/workflow.yml from 5.4.3 to 5.5.7.
Release notes
Sourced from PSModule/Process-PSModule/.github/workflows/workflow.yml's releases.
... (truncated)
Commits
ce64918Bump PSModule/GitHub-Script from 1.7.10 to 1.8.0 (#346)dcfb311Bump PSModule/Build-PSModule from 4.0.14 to 4.0.15 (#345)762cffbBump PSModule/Invoke-Pester from 4.2.4 to 4.2.5 (#344)8bb1745Bump actions/upload-pages-artifact from 4.0.0 to 5.0.0 (#340)e34ef35Bump actions/upload-artifact from 7.0.0 to 7.0.1 (#341)e8f5b22🩹 [Patch]: Bump PSModule/Publish-PSModule to v2.2.4 (#312)51f27f7🩹 [Patch]: Reusable workflow dependencies updated (#332)1111791🚀 [Feature]: Release-triggering file patterns now configurable via workflow i...3ed96da🩹 [Patch]: Framework-generated code coverage no longer penalizes module autho...205d193🪲 [Fix]: Super-linter can now post PR comment summaries (#308)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)