v2.1.0
🚀 [Feature]: Add PR-based release name and notes options (#58)
The publish action now supports using your pull request title and description to create more meaningful GitHub releases, giving you control over how your module releases appear to users.
- Relates to PSModule/Process-PSModule#263
New action inputs
Three new inputs are available in the action:
| Input | Default | Description |
|---|---|---|
UsePRTitleAsReleaseName |
false |
Uses the pull request title as the name for the GitHub release |
UsePRBodyAsReleaseNotes |
true |
Uses the pull request body as the release notes content |
UsePRTitleAsNotesHeading |
true |
Prepends PR title as H1 heading with PR number link in release notes |
Default behavior
With default settings, when a module is published:
- The release name uses the version tag (e.g.,
v1.2.3) - The release notes include the PR title as a heading with a link to the PR
- The PR description follows as the release notes body
- Falls back to GitHub's auto-generated notes if the PR description is empty
Implementation details
The release creation logic in scripts/helpers/Publish-PSModule.ps1 now dynamically builds the gh release create command based on the configuration:
- Adds
--titlewith PR title whenUsePRTitleAsReleaseNameis enabled - Adds
--noteswith formatted content when PR body is available - Falls back to
--generate-noteswhen no PR content is available
Linting improvements
- Disabled
BIOME_FORMATvalidation via.github/PSModule.yml - Added
persist-credentials: falseto all checkout steps - Added
groupsconfiguration to dependabot for cooldown compliance - Added
zizmor: ignorecomments for intentional patterns (dangerous-triggers, unpinned external actions)