Skip to content

🪲 [Fix]: Resolve to the current version on non-PR events (workflow_dispatch, schedule)#10

Merged
Marius Storhaug (MariusStorhaug) merged 2 commits into
mainfrom
fix/non-pr-events-use-current-version
Jul 11, 2026
Merged

🪲 [Fix]: Resolve to the current version on non-PR events (workflow_dispatch, schedule)#10
Marius Storhaug (MariusStorhaug) merged 2 commits into
mainfrom
fix/non-pr-events-use-current-version

Conversation

@MariusStorhaug

@MariusStorhaug Marius Storhaug (MariusStorhaug) commented Jul 11, 2026

Copy link
Copy Markdown
Member

On non–pull-request events (for example workflow_dispatch and schedule), the action now resolves to the current published version instead of throwing. This is the root-cause fix for the Plan failures consumers see on scheduled and manual runs.

Fixed: no more throw on non–pull-request events

Previously the action required a pull_request payload and threw "...must be run from a pull_request event" on any other event. Because Process-PSModule's Plan job runs this on every event, that failed the whole run on schedule / workflow_dispatch for every consumer.

Now, when the event has no pull_request, Get-GitHubPullRequest returns $null and the caller resolves a no-op decision: no bump, no prerelease, nothing published — so Get-NextModuleVersion returns the current published version unchanged.

New: non-PR runs report the current version

There are no PR labels on workflow_dispatch / schedule, so there's nothing to bump from. The action keeps the latest published version (GitHub Release / PS Gallery), which is what a scheduled or manual re-test should build and test against. For a module that has never been released this floors at 0.0.0. Pull-request and merge-to-default-branch behavior is unchanged — labels drive the bump, with patch as the default.

Technical Details

  • scripts/Resolve-PSModuleVersion.Helpers.psm1: Get-GitHubPullRequest returns $null on a non-PR event instead of throwing.
  • scripts/main.ps1: builds a no-op release decision (all flags false, empty prerelease) when there is no pull request, otherwise calls Resolve-ReleaseDecision as before. Get-NextModuleVersion then returns LatestVersion unchanged.
  • tests/: added cases asserting the no-op decision keeps the current version (1.2.3 and the 0.0.0 floor) with no bump and no prerelease. Full suite: 159 passed, PSScriptAnalyzer clean.
  • Follow-up: once released, Process-PSModule bumps its Resolve-Version pin to this version, which lets its Plan.yml gate + 999.0.0 fallback in PR #375 be dropped.

Copilot AI review requested due to automatic review settings July 11, 2026 11:36
Merged
Copilot AI reviewed Jul 11, 2026
View reviewed changes

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Resolve-PSModuleVersion GitHub Action to support non–pull-request workflow events (e.g., workflow_dispatch, schedule) by treating them as a no-op release decision and resolving to the current published module version instead of throwing.

Changes:

  • Get-GitHubPullRequest now returns $null (instead of throwing) when the event payload has no pull_request.
  • scripts/main.ps1 now builds a no-op release decision when no PR context exists, keeping the latest published version unchanged.
  • Adds Pester coverage asserting the no-op decision results in no bump and no prerelease.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File Description
tests/Resolve-PSModuleVersion.Helpers.Tests.ps1 Adds tests for non-PR behavior keeping the current version unchanged.
scripts/Resolve-PSModuleVersion.Helpers.psm1 Changes non-PR handling in Get-GitHubPullRequest from throwing to returning $null.
scripts/main.ps1 Handles $null PR context by using a no-op decision so non-PR events resolve to the current version.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread scripts/Resolve-PSModuleVersion.Helpers.psm1
Comment thread tests/Resolve-PSModuleVersion.Helpers.Tests.ps1
Copilot AI review requested due to automatic review settings July 11, 2026 12:30
Copilot AI reviewed Jul 11, 2026
View reviewed changes

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Copilot AI reviewed Jul 11, 2026
View reviewed changes

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

@MariusStorhaug Marius Storhaug (MariusStorhaug) merged commit 6a59a88 into main Jul 11, 2026
19 checks passed
@MariusStorhaug Marius Storhaug (MariusStorhaug) deleted the fix/non-pr-events-use-current-version branch July 11, 2026 13:21
Marius Storhaug (MariusStorhaug) added a commit to PSModule/Process-PSModule that referenced this pull request Jul 11, 2026
@MariusStorhaug
🪲 [Fix]: Resolve the current version on non-PR runs (bump Resolve-PSM…
da180ba 
…oduleVersion to v1.1.5) (#375)

The `Plan` job no longer fails on `schedule` and `workflow_dispatch`
events. `Resolve-PSModuleVersion` is bumped to `v1.1.5`, which resolves
the current published version on non–pull-request events instead of
throwing.

- Fixes #373

## Fixed: non–pull-request runs (schedule / workflow_dispatch)

Since v6.1.0 the `Plan` job runs `Resolve-Version` on every event, and
the action threw `"...must be run from a pull_request event"` on non-PR
events — failing the whole run (every job `needs: Plan`).
`Resolve-PSModuleVersion` `v1.1.5` (PSModule/Resolve-PSModuleVersion#10)
fixes this at the source: on a non-PR event it returns the current
published version — no bump, no prerelease, nothing published — floored
at `0.0.0` for a module that has never been released. Pull-request and
merge-to-default-branch behavior is unchanged: labels drive the bump
(patch default), and the version preview on regular PRs is retained.

## Technical Details

- `.github/workflows/Plan.yml`: bump the `Resolve-Version` pin `8d1dac7`
(`v1.1.4`) → `6a59a88` (`v1.1.5`). One-line change — no `Plan` gate or
`Test-ModuleLocal` fallback is needed, because v1.1.5 always populates
`Settings.Module.Version` on non-PR events.
- This supersedes this PR's earlier `Plan.yml` gate + `999.0.0` fallback
approach, replaced by the root-cause fix in the shared action.
- Validated: a `workflow_dispatch` self-test run on this branch
completes (previously failed at `Plan`); the PR self-test resolves a
version as before.
Marius Storhaug (MariusStorhaug) pushed a commit to PSModule/Sodium that referenced this pull request Jul 14, 2026
@dependabot
Bump PSModule/Process-PSModule/.github/workflows/workflow.yml from 5.…
8bcbff4 
…5.2 to 6.1.4 (#68)

Bumps
[PSModule/Process-PSModule/.github/workflows/workflow.yml](https://github.com/psmodule/process-psmodule)
from 5.5.2 to 6.1.4.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/psmodule/process-psmodule/releases">PSModule/Process-PSModule/.github/workflows/workflow.yml's
releases</a>.</em></p>
<blockquote>
<h2>v6.1.4</h2>
<h1>🪲 [Fix]: Resolve the current version on non-PR runs (bump
Resolve-PSModuleVersion to v1.1.5) (<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/375">#375</a>)</h1>
<p>The <code>Plan</code> job no longer fails on <code>schedule</code>
and <code>workflow_dispatch</code> events.
<code>Resolve-PSModuleVersion</code> is bumped to <code>v1.1.5</code>,
which resolves the current published version on non–pull-request events
instead of throwing.</p>
<ul>
<li>Fixes <a
href="https://redirect.github.com/psmodule/process-psmodule/issues/373">#373</a></li>
</ul>
<h2>Fixed: non–pull-request runs (schedule / workflow_dispatch)</h2>
<p>Since v6.1.0 the <code>Plan</code> job runs
<code>Resolve-Version</code> on every event, and the action threw
<code>&quot;...must be run from a pull_request event&quot;</code> on
non-PR events — failing the whole run (every job <code>needs:
Plan</code>). <code>Resolve-PSModuleVersion</code>
<code>v1.1.5</code><code>PSModule/Resolve-PSModuleVersion#10</code><code>0.0.0</code>
for a module that has never been released. Pull-request and
merge-to-default-branch behavior is unchanged: labels drive the bump
(patch default), and the version preview on regular PRs is retained.</p>
<h2>Technical Details</h2>
<ul>
<li><code>.github/workflows/Plan.yml</code>: bump the
<code>Resolve-Version</code> pin <code>8d1dac7</code>
(<code>v1.1.4</code>) → <code>6a59a88</code> (<code>v1.1.5</code>).
One-line change — no <code>Plan</code> gate or
<code>Test-ModuleLocal</code> fallback is needed, because v1.1.5 always
populates <code>Settings.Module.Version</code> on non-PR events.</li>
<li>This supersedes this PR's earlier <code>Plan.yml</code> gate +
<code>999.0.0</code> fallback approach, replaced by the root-cause fix
in the shared action.</li>
<li>Validated: a <code>workflow_dispatch</code> self-test run on this
branch completes (previously failed at <code>Plan</code>); the PR
self-test resolves a version as before.</li>
</ul>
<h2>v6.1.3</h2>
<h1>🩹 [Patch]: Bump Invoke-ScriptAnalyzer to v5.0.0 and Test-PSModule to
v3.0.14 (<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/380">#380</a>)</h1>
<p>Brings Process-PSModule's lint/test action dependencies to their
latest releases: <code>PSModule/Invoke-ScriptAnalyzer</code> v4.1.3 →
v5.0.0 and <code>PSModule/Test-PSModule</code> v3.0.13 → v3.0.14. Both
preserve the reusable workflow's
<code>Settings.Version</code>/<code>Settings.Prerelease</code> contract
for consumers.</p>
<h2>Changed: Invoke-ScriptAnalyzer upgraded to v5.0.0</h2>
<p>Invoke-ScriptAnalyzer v5.0.0 is a major release that repurposed its
<code>Version</code>/<code>Prerelease</code> inputs to select the
<strong>PSScriptAnalyzer</strong> module version and moved the GitHub
bootstrap-module controls to
<code>GitHubVersion</code>/<code>GitHubPrerelease</code>.</p>
<p>The <code>Lint-SourceCode</code> and <code>Lint-Module</code> steps
pass <code>Settings.Version</code>/<code>Settings.Prerelease</code>,
which in this ecosystem select the <strong>GitHub module</strong> (the
same values feed the Invoke-Pester and GitHub-Script steps). They are
now wired to Invoke-ScriptAnalyzer's
<code>GitHubVersion</code>/<code>GitHubPrerelease</code>, so those
settings keep controlling the GitHub module exactly as before. No change
to the <code>Settings</code> contract.</p>
<p>With v5, the action also installs PSScriptAnalyzer itself (latest,
since its <code>Version</code> is left unset) instead of relying on the
runner's preinstalled copy — so consumer linting now runs against the
latest PSScriptAnalyzer.</p>
<h2>Changed: Test-PSModule upgraded to v3.0.14</h2>
<p>Patch release; Test-PSModule v3.0.14 (which internally bumped
Invoke-Pester to v5.1.0) preserves its own
<code>Version</code>/<code>Prerelease</code> (GitHub module) contract,
so the <code>Test-SourceCode</code> and <code>Test-Module</code> steps
need only a SHA update — no input remap.</p>
<h2>Technical Details</h2>
<ul>
<li><code>Lint-SourceCode.yml</code>, <code>Test-Module.yml</code>:
<code>Invoke-ScriptAnalyzer</code> <code>6aeb1bc</code> (v4.1.3) →
<code>4d633e4</code> (v5.0.0); remapped <code>Version</code> →
<code>GitHubVersion</code>, <code>Prerelease</code> →
<code>GitHubPrerelease</code>.</li>
<li><code>Test-Module.yml</code>, <code>Test-SourceCode.yml</code>:
<code>Test-PSModule</code> <code>25c9cd8</code> (v3.0.13) →
<code>902c5e5</code> (v3.0.14).</li>
<li>Pester and PSScriptAnalyzer versions left at the v5 defaults
(latest); not wired to any <code>Settings</code> key.</li>
<li>Scope: the Invoke-Pester step (<code>Test-ModuleLocal.yml</code>,
still v4.2.6) is intentionally untouched.</li>
<li>Label note: the <code>Settings</code> contract is preserved (hence
<code>Patch</code>), but consumer linting now runs against the latest
PSScriptAnalyzer — bump to <code>Minor</code> if you'd rather signal
that behavior change.</li>
</ul>
<p>Release notes: <a
href="https://github.com/PSModule/Invoke-ScriptAnalyzer/releases/tag/v5.0.0">Invoke-ScriptAnalyzer
v5.0.0</a></p>
<h2>v6.1.2</h2>
<h1>🪲 [Fix]: Test data reaches module tests in every consumer repository
(<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/377">#377</a>)</h1>
<p>Module test workflows now receive the caller-provided test data
(secrets and variables) in every repository that consumes
Process-PSModule, and version resolution once again honors the bump
label on pull requests. Previously the BeforeAll, Test, and AfterAll
module jobs failed at the &quot;Expose caller-provided test data&quot;
step because they ran a script that shipped only inside
Process-PSModule's own repository, so no consumer could actually use the
<code>TestData</code> secret introduced in v6.0.0.</p>
<ul>
<li>Fixes <a
href="https://redirect.github.com/psmodule/process-psmodule/issues/378">#378</a></li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/da180bac16b13bfbcdf08b2e4e221b5b49e5ff28"><code>da180ba</code></a>
🪲 [Fix]: Resolve the current version on non-PR runs (bump
Resolve-PSModuleVer...</li>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/06fd9added53d9b99031cc0aef86ebfda4fd69aa"><code>06fd9ad</code></a>
🩹 [Patch]: Bump Invoke-ScriptAnalyzer to v5.0.0 and Test-PSModule to
v3.0.14 ...</li>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/d4020f3c9c3621cebae5d8bf4ffaf10f55c1784a"><code>d4020f3</code></a>
🪲 [Fix]: Test data reaches module tests in every consumer repository (<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/377">#377</a>)</li>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/ea19a3eb1293246d1b00e4faae1544442c3be0ec"><code>ea19a3e</code></a>
🩹 [Patch]: Render group overview pages as section landing pages (<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/372">#372</a>)</li>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/0d7a2f0b9422ad727886d1ef79d1874ccc358fd7"><code>0d7a2f0</code></a>
🚀 [Feature]: Plan job decides version before build so tested artifact
equals ...</li>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/54e2677755efd41a80f2138ec147cffb1a5923b2"><code>54e2677</code></a>
Bump PSModule/GitHub-Script from 1.8.0 to 1.9.0 (<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/367">#367</a>)</li>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/1514ac0ffa1168256ab0476e8ad357d6a4e8f96f"><code>1514ac0</code></a>
📖 [Docs]: Add full dependency tree with Mermaid diagrams (<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/368">#368</a>)</li>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/364ddd65e7de2c04bc1b526974fd1a0f5097b123"><code>364ddd6</code></a>
🌟 [Major]: Fixed test secret inputs replaced by TestData (<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/365">#365</a>)</li>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/8b7553757b50e2e265a12bc3b0bab2078c5b3fea"><code>8b75537</code></a>
🪲 [Fix]: Restore correct release versioning in the publish pipeline (<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/363">#363</a>)</li>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/6aa7664d5ceab1314e4988ee879ebad19037662b"><code>6aa7664</code></a>
📖 [Docs]: Document the Pester major-version lock in the test pipeline
(<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/362">#362</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/psmodule/process-psmodule/compare/e8f5b22925c5a4dcf462d8b212570b66ce6a8df4...da180bac16b13bfbcdf08b2e4e221b5b49e5ff28">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=PSModule/Process-PSModule/.github/workflows/workflow.yml&package-manager=github_actions&previous-version=5.5.2&new-version=6.1.4)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Marius Storhaug (MariusStorhaug) pushed a commit to PSModule/Confluence that referenced this pull request Jul 14, 2026
@dependabot
Bump PSModule/Process-PSModule/.github/workflows/workflow.yml from 5.…
e9bc190 
…5.7 to 6.1.4 (#19)

Bumps
[PSModule/Process-PSModule/.github/workflows/workflow.yml](https://github.com/psmodule/process-psmodule)
from 5.5.7 to 6.1.4.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/psmodule/process-psmodule/releases">PSModule/Process-PSModule/.github/workflows/workflow.yml's
releases</a>.</em></p>
<blockquote>
<h2>v6.1.4</h2>
<h1>🪲 [Fix]: Resolve the current version on non-PR runs (bump
Resolve-PSModuleVersion to v1.1.5) (<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/375">#375</a>)</h1>
<p>The <code>Plan</code> job no longer fails on <code>schedule</code>
and <code>workflow_dispatch</code> events.
<code>Resolve-PSModuleVersion</code> is bumped to <code>v1.1.5</code>,
which resolves the current published version on non–pull-request events
instead of throwing.</p>
<ul>
<li>Fixes <a
href="https://redirect.github.com/psmodule/process-psmodule/issues/373">#373</a></li>
</ul>
<h2>Fixed: non–pull-request runs (schedule / workflow_dispatch)</h2>
<p>Since v6.1.0 the <code>Plan</code> job runs
<code>Resolve-Version</code> on every event, and the action threw
<code>&quot;...must be run from a pull_request event&quot;</code> on
non-PR events — failing the whole run (every job <code>needs:
Plan</code>). <code>Resolve-PSModuleVersion</code>
<code>v1.1.5</code><code>PSModule/Resolve-PSModuleVersion#10</code><code>0.0.0</code>
for a module that has never been released. Pull-request and
merge-to-default-branch behavior is unchanged: labels drive the bump
(patch default), and the version preview on regular PRs is retained.</p>
<h2>Technical Details</h2>
<ul>
<li><code>.github/workflows/Plan.yml</code>: bump the
<code>Resolve-Version</code> pin <code>8d1dac7</code>
(<code>v1.1.4</code>) → <code>6a59a88</code> (<code>v1.1.5</code>).
One-line change — no <code>Plan</code> gate or
<code>Test-ModuleLocal</code> fallback is needed, because v1.1.5 always
populates <code>Settings.Module.Version</code> on non-PR events.</li>
<li>This supersedes this PR's earlier <code>Plan.yml</code> gate +
<code>999.0.0</code> fallback approach, replaced by the root-cause fix
in the shared action.</li>
<li>Validated: a <code>workflow_dispatch</code> self-test run on this
branch completes (previously failed at <code>Plan</code>); the PR
self-test resolves a version as before.</li>
</ul>
<h2>v6.1.3</h2>
<h1>🩹 [Patch]: Bump Invoke-ScriptAnalyzer to v5.0.0 and Test-PSModule to
v3.0.14 (<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/380">#380</a>)</h1>
<p>Brings Process-PSModule's lint/test action dependencies to their
latest releases: <code>PSModule/Invoke-ScriptAnalyzer</code> v4.1.3 →
v5.0.0 and <code>PSModule/Test-PSModule</code> v3.0.13 → v3.0.14. Both
preserve the reusable workflow's
<code>Settings.Version</code>/<code>Settings.Prerelease</code> contract
for consumers.</p>
<h2>Changed: Invoke-ScriptAnalyzer upgraded to v5.0.0</h2>
<p>Invoke-ScriptAnalyzer v5.0.0 is a major release that repurposed its
<code>Version</code>/<code>Prerelease</code> inputs to select the
<strong>PSScriptAnalyzer</strong> module version and moved the GitHub
bootstrap-module controls to
<code>GitHubVersion</code>/<code>GitHubPrerelease</code>.</p>
<p>The <code>Lint-SourceCode</code> and <code>Lint-Module</code> steps
pass <code>Settings.Version</code>/<code>Settings.Prerelease</code>,
which in this ecosystem select the <strong>GitHub module</strong> (the
same values feed the Invoke-Pester and GitHub-Script steps). They are
now wired to Invoke-ScriptAnalyzer's
<code>GitHubVersion</code>/<code>GitHubPrerelease</code>, so those
settings keep controlling the GitHub module exactly as before. No change
to the <code>Settings</code> contract.</p>
<p>With v5, the action also installs PSScriptAnalyzer itself (latest,
since its <code>Version</code> is left unset) instead of relying on the
runner's preinstalled copy — so consumer linting now runs against the
latest PSScriptAnalyzer.</p>
<h2>Changed: Test-PSModule upgraded to v3.0.14</h2>
<p>Patch release; Test-PSModule v3.0.14 (which internally bumped
Invoke-Pester to v5.1.0) preserves its own
<code>Version</code>/<code>Prerelease</code> (GitHub module) contract,
so the <code>Test-SourceCode</code> and <code>Test-Module</code> steps
need only a SHA update — no input remap.</p>
<h2>Technical Details</h2>
<ul>
<li><code>Lint-SourceCode.yml</code>, <code>Test-Module.yml</code>:
<code>Invoke-ScriptAnalyzer</code> <code>6aeb1bc</code> (v4.1.3) →
<code>4d633e4</code> (v5.0.0); remapped <code>Version</code> →
<code>GitHubVersion</code>, <code>Prerelease</code> →
<code>GitHubPrerelease</code>.</li>
<li><code>Test-Module.yml</code>, <code>Test-SourceCode.yml</code>:
<code>Test-PSModule</code> <code>25c9cd8</code> (v3.0.13) →
<code>902c5e5</code> (v3.0.14).</li>
<li>Pester and PSScriptAnalyzer versions left at the v5 defaults
(latest); not wired to any <code>Settings</code> key.</li>
<li>Scope: the Invoke-Pester step (<code>Test-ModuleLocal.yml</code>,
still v4.2.6) is intentionally untouched.</li>
<li>Label note: the <code>Settings</code> contract is preserved (hence
<code>Patch</code>), but consumer linting now runs against the latest
PSScriptAnalyzer — bump to <code>Minor</code> if you'd rather signal
that behavior change.</li>
</ul>
<p>Release notes: <a
href="https://github.com/PSModule/Invoke-ScriptAnalyzer/releases/tag/v5.0.0">Invoke-ScriptAnalyzer
v5.0.0</a></p>
<h2>v6.1.2</h2>
<h1>🪲 [Fix]: Test data reaches module tests in every consumer repository
(<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/377">#377</a>)</h1>
<p>Module test workflows now receive the caller-provided test data
(secrets and variables) in every repository that consumes
Process-PSModule, and version resolution once again honors the bump
label on pull requests. Previously the BeforeAll, Test, and AfterAll
module jobs failed at the &quot;Expose caller-provided test data&quot;
step because they ran a script that shipped only inside
Process-PSModule's own repository, so no consumer could actually use the
<code>TestData</code> secret introduced in v6.0.0.</p>
<ul>
<li>Fixes <a
href="https://redirect.github.com/psmodule/process-psmodule/issues/378">#378</a></li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/da180bac16b13bfbcdf08b2e4e221b5b49e5ff28"><code>da180ba</code></a>
🪲 [Fix]: Resolve the current version on non-PR runs (bump
Resolve-PSModuleVer...</li>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/06fd9added53d9b99031cc0aef86ebfda4fd69aa"><code>06fd9ad</code></a>
🩹 [Patch]: Bump Invoke-ScriptAnalyzer to v5.0.0 and Test-PSModule to
v3.0.14 ...</li>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/d4020f3c9c3621cebae5d8bf4ffaf10f55c1784a"><code>d4020f3</code></a>
🪲 [Fix]: Test data reaches module tests in every consumer repository (<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/377">#377</a>)</li>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/ea19a3eb1293246d1b00e4faae1544442c3be0ec"><code>ea19a3e</code></a>
🩹 [Patch]: Render group overview pages as section landing pages (<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/372">#372</a>)</li>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/0d7a2f0b9422ad727886d1ef79d1874ccc358fd7"><code>0d7a2f0</code></a>
🚀 [Feature]: Plan job decides version before build so tested artifact
equals ...</li>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/54e2677755efd41a80f2138ec147cffb1a5923b2"><code>54e2677</code></a>
Bump PSModule/GitHub-Script from 1.8.0 to 1.9.0 (<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/367">#367</a>)</li>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/1514ac0ffa1168256ab0476e8ad357d6a4e8f96f"><code>1514ac0</code></a>
📖 [Docs]: Add full dependency tree with Mermaid diagrams (<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/368">#368</a>)</li>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/364ddd65e7de2c04bc1b526974fd1a0f5097b123"><code>364ddd6</code></a>
🌟 [Major]: Fixed test secret inputs replaced by TestData (<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/365">#365</a>)</li>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/8b7553757b50e2e265a12bc3b0bab2078c5b3fea"><code>8b75537</code></a>
🪲 [Fix]: Restore correct release versioning in the publish pipeline (<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/363">#363</a>)</li>
<li><a
href="https://github.com/PSModule/Process-PSModule/commit/6aa7664d5ceab1314e4988ee879ebad19037662b"><code>6aa7664</code></a>
📖 [Docs]: Document the Pester major-version lock in the test pipeline
(<a
href="https://redirect.github.com/psmodule/process-psmodule/issues/362">#362</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/psmodule/process-psmodule/compare/ce64918acc96dda73eb78f827036b794bfa6fa1a...da180bac16b13bfbcdf08b2e4e221b5b49e5ff28">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=PSModule/Process-PSModule/.github/workflows/workflow.yml&package-manager=github_actions&previous-version=5.5.7&new-version=6.1.4)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@MariusStorhaug