Skip to content

Bump PSModule/Process-PSModule/.github/workflows/workflow.yml from 6.1.13 to 6.1.14 - #1

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/PSModule/Process-PSModule/dot-github/workflows/workflow.yml-6.1.14
Closed

Bump PSModule/Process-PSModule/.github/workflows/workflow.yml from 6.1.13 to 6.1.14#1
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/PSModule/Process-PSModule/dot-github/workflows/workflow.yml-6.1.14

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 2, 2026

Copy link
Copy Markdown

Bumps PSModule/Process-PSModule/.github/workflows/workflow.yml from 6.1.13 to 6.1.14.

Release notes

Sourced from PSModule/Process-PSModule/.github/workflows/workflow.yml's releases.

v6.1.14

⚙️ [Maintenance]: Public help links follow canonical documentation paths (#420)

Public module source validation requires each public function-bearing script under src/functions/public to put its canonical generated-documentation URL first in comment-based help.

Changed: Canonical public help links are enforced for function-bearing files

The source-code standards suite derives documentation paths from recursive public function paths and validates the first .LINK against https://psmodule.io/<ModuleName>/Functions/<relative path>/<FunctionName>/.

Technical Details

  • Test-SourceCode forwards the configured module name into the shared test action instead of falling back to the repository name.
  • Public help-link validation applies only to public scripts that define at least one function/filter.
  • Covers ungrouped and nested public function scripts.
  • Requires at least one .LINK, exact URL casing/content, first-link ordering, and a trailing slash.
  • Fixture repos cover both grouped and ungrouped function paths while non-function public scripts are not forced to provide canonical links.

Downstream dependency status (live)

  • PSModule/Domeneshop PR #17 has already been merged into main at 2ca6f788c4b68a72c63d6472ae19720bc90cc8b9 while still pinned to Process-PSModule v6.1.13 (fb1bdb8fefd243292f779d2a856a38db6fe6daf4).
  • That downstream state currently lacks the local PublicHelpLinks / ModuleRequirements / TestLayout checks intended by this framework update.
  • Merging this PR unblocks downstream alignment by making the canonical public help-link validation available in the framework version line.

Validation

  • Focused PublicHelpLink runs pass for both dynamic module names (4 cases each after scoping).
  • Full source-code standards suites pass for both fixtures (13 tests each).
  • PSScriptAnalyzer reports no warnings or errors in changed files.
  • Draft PR CI passes, including linter, CodeQL, action analysis, and both workflow-test matrices.
Commits
  • b11b310 ⚙️ [Maintenance]: Public help links follow canonical documentation paths (#420)
  • 9bca3f5 ⚙️ [Maintenance]: Module source tests align with latest PowerShell LTS (#419)
  • See full diff in compare view

Dependabot compatibility score

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 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)

Bumps [PSModule/Process-PSModule/.github/workflows/workflow.yml](https://github.com/psmodule/process-psmodule) from 6.1.13 to 6.1.14.
- [Release notes](https://github.com/psmodule/process-psmodule/releases)
- [Commits](PSModule/Process-PSModule@fb1bdb8...b11b310)

---
updated-dependencies:
- dependency-name: PSModule/Process-PSModule/.github/workflows/workflow.yml
  dependency-version: 6.1.14
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Aug 2, 2026

Copy link
Copy Markdown
Author

Labels

The following labels could not be found: dependencies, github-actions. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown

No Significant Changes Detected

This PR does not contain changes to files that would trigger a new release:

Pattern Description
^src/ Matches files where path matches this pattern
^README\.md$ Matches files where path matches this pattern

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.

Marius Storhaug (MariusStorhaug) added a commit to PSModule/Process-PSModule that referenced this pull request Aug 2, 2026
…eleases (#432)

A module repository that has not published its first release no longer
breaks. Previously the `Plan` job failed on any repository with zero
GitHub releases, which meant every brand-new module created from the
template was blocked on its very first pull request — a chicken-and-egg
problem where the framework could not run until a release existed, and a
release could not be created until the framework ran.

## Fixed: Version resolution works before the first release exists

A repository with no GitHub releases, and a module that has never been
published to the PowerShell Gallery, now resolve cleanly to a `0.0.0`
baseline. The first labelled pull request produces the expected first
version — `0.0.1` for a patch, `0.1.0` for a minor, `1.0.0` for a major
— instead of failing the `Plan` job with:

```text
Cannot bind argument to parameter 'Releases' because it is null.
```

Because every downstream job depends on `Plan`, that failure skipped the
whole run and made the pull request unmergeable. Nothing needs to change
in consuming repositories; bumping to the released version is enough.

---
<details>
<summary>Technical details</summary>

- Verified the reported diagnosis before changing anything. Both
`Get-LatestGitHubVersion -Releases $null` **and**
`Get-LatestGitHubVersion -Releases @()` failed. `[Parameter(Mandatory)]
[array]` rejects an empty collection as well as `$null`, so normalising
at the call site with `@(Get-GitHubRelease)` alone would have turned the
null error into an "empty collection" error. The parameter declarations
had to be relaxed too.
- `Resolve-PSModuleVersion.Helpers.psm1`: `Releases` on
`Get-LatestGitHubVersion`, `Get-NextPrereleaseNumber`, and
`Get-NextModuleVersion` is now optional with `[AllowNull()]`,
`[AllowEmptyCollection()]`, and an `@()` default, so each function is
individually robust rather than depending on a careful caller.
- New `ConvertFrom-GitHubReleaseJson` owns the normalisation of the `gh
release list` output into a flat array, including the case where the
command produced no output at all (the second reproduction in #381,
where a repository with five releases still yielded `$null`).
`Get-GitHubRelease` delegates to it and `src/main.ps1` normalises with
`$releases = @(Get-GitHubRelease)`.
- `Get-LatestPublishedVersion` accepts null versions and filters empty
candidates before sorting, warning and flooring to `0.0.0` when neither
source has a version. `Get-NextModuleVersion` accepts a null
`LatestVersion` and floors it to `0.0.0`.
- The downstream fallback logic was already correct — only parameter
binding, null handling, and the array shape changed. Version resolution
was not redesigned.
- Tests:
`.github/actions/Resolve-PSModuleVersion/tests/Resolve-PSModuleVersion.Helpers.Tests.ps1`
adds 36 Pester tests following the [test
specification](https://psmodule.io/docs/Modules/Test-Specification/). 21
of them fail against the previous parameter declarations. They cover a
null releases list, an empty releases list, releases with none marked
`isLatest`, prerelease-only repositories, the release-JSON
normalisation, and the full brand-new-module chain for major, minor, and
patch decisions.
- CI: `.github/workflows/Test-Actions.yml` runs every
`.github/actions/*/tests` folder with Pester on pull requests that touch
an action, so the repository now has a unit-test surface for its own
actions.
- Standards and framework alignment:

| Changed surface | Standards checked | Framework docs checked | Result
|
| --- | --- | --- | --- |
| `.github/actions/Resolve-PSModuleVersion/src/**` | PSScriptAnalyzer
via `.github/linters/.powershell-psscriptanalyzer.psd1` | PSModule
function/parameter conventions | Aligned |
| `.github/actions/Resolve-PSModuleVersion/tests/**` | PSScriptAnalyzer
| [Test
Specification](https://psmodule.io/docs/Modules/Test-Specification/) |
Aligned |
| `.github/workflows/Test-Actions.yml` | Pinned action SHAs,
least-privilege permissions | Reusable workflow contract | Aligned —
repository-internal workflow, not consumer-facing |

</details>

<details>
<summary>Relevant issues (or links)</summary>

- Fixes #381
- #433 — follow-up for end-to-end coverage of a
repository with zero releases
- Reproduction: PSModule/Lovdata#1 — [failing run
30743884958](https://github.com/PSModule/Lovdata/actions/runs/30743884958/job/91486012154)

</details>

---------

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@dependabot @github

dependabot Bot commented on behalf of github Aug 2, 2026

Copy link
Copy Markdown
Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/github_actions/PSModule/Process-PSModule/dot-github/workflows/workflow.yml-6.1.14 branch August 2, 2026 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant