🩹[Patch]: Workflow improvements

[MariusStorhaug]

This release makes several improvements to the release workflow and supporting scripts, focusing on standardization, clarity, and modernization. The most significant changes include renaming and updating the release workflow, consolidating and improving PowerShell scripts, and cleaning up configuration files related to linters and release notes. Additionally, the scripts now use Write-Host for output and include more structured and readable logging.

Release Workflow Improvements

• Renamed the workflow file from .github/workflows/Auto-Release.yml to .github/workflows/Release.yml, updated the workflow name and job names, and switched from the Auto-Release action to the newer Release-GHRepository action for publishing releases. Also, restricted the workflow to trigger only on changes to action.yml and src/**.

PowerShell Script Modernization and Consolidation

• Moved PowerShell scripts from the scripts/ directory to src/, updated references in action.yml, and improved script output by replacing Write-Output with Write-Host for better compatibility with GitHub Actions. Added more structured and visually separated log output using Write-Host '-------------------------------------------------'.

Configuration and Linting Cleanup

• Removed the .github/linters/.jscpd.json configuration file and disabled JSCPD validation in the linter workflow.
• Added an exclusion for the PSAvoidUsingWriteHost rule in .github/linters/.powershell-psscriptanalyzer.psd1 to allow using Write-Host in scripts running on GitHub Actions.

Release Notes and Input Documentation

• Removed the custom changelog configuration from .github/release.yml to rely on default GitHub release note generation.
• Fixed a typo in the IncrementalPrerelease input description in action.yml.

[Copilot]

Pull request overview

This PR removes the deprecated .github/release.yml configuration file as the release configuration has been migrated to the action's input parameters.

Changes:

• Removed .github/release.yml file containing changelog configuration for automatically generated release notes

---

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

[Copilot]

Pull request overview

Copilot reviewed 3 out of 6 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

.github/workflows/Release.yml:18

• The scope of this PR is described as removing the deprecated .github/release.yml configuration, but the changes also introduce new PowerShell scripts under src/, switch the composite action to use those scripts, and adjust the Release workflow’s name, job ID, and path filters. It would be helpful for future maintainers if the PR description (and/or commit message) were updated to reflect these broader behavior and structure changes, not just the removal of the release configuration file.

---

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

[Copilot]

Pull request overview

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

---

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

[Copilot]

Pull request overview

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

Comments suppressed due to low confidence (1)

src/publish.ps1:192

• This Write-Host notice now includes $releaseURL, but $releaseURL is only assigned in the non-WhatIf branch above. When WhatIf is true, this line will still log a "New release" notice with an empty URL even though no release was created, which is misleading for consumers of this action. Consider either skipping this notice when WhatIf is enabled or emitting a distinct "WhatIf"-specific message that does not reference $releaseURL.

---

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

[Copilot]

Pull request overview

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

---

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

[Copilot]

Pull request overview

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

Comments suppressed due to low confidence (4)

src/publish.ps1:123

• In the WhatIf branch, the gh pr comment command string is built using a single-quoted literal on the second part, so $releaseType, $name, $publishPSVersion, and $psGalleryReleaseLink will not be interpolated and the logged command will show the variable names instead of their values. To make the WhatIf output accurately reflect the command that would be run, consider switching this inner string to an interpolated form (e.g., double-quoted or -f formatting) so the variables are expanded.
  src/publish.ps1:201
• Similarly to the PSGallery WhatIf output, this gh pr comment command string in the WhatIf branch uses a single-quoted literal, so $releaseType, $name, and $newVersion will not be interpolated and the logged command will show literal variable names. For more useful diagnostics in WhatIf mode, it would be better to build this string in a way that expands those variables (for example by using a double-quoted string or -f formatting).
  src/publish.ps1:127
• In these success messages, there is an unmatched backtick immediately after $releaseType (e.g., ✅ New release: PowerShell Gallery - ...), which will show up literally in the rendered notice/comment and likely isn’t intended. Consider either removing the backtick or wrapping the release type in matching backticks if you want inline-code formatting.
  src/publish.ps1:210
• These GitHub release notifications also include an unmatched backtick immediately after $releaseType in both the PR comment body and the ::notice title, so the rendered text will appear with a stray ` character (e.g., ✅ New prerelease: GitHub - ...). If that isn’t intentional, consider removing the backtick or adding a matching one to get proper inline-code formatting around the release type.

---

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

[Copilot]

Pull request overview

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

Comments suppressed due to low confidence (1)

src/publish.ps1:209

• In the New-GitHubRelease log group, the final notice message is always emitted, but $releaseURL is only assigned inside the else branch when $whatIf is $false. In WhatIf mode this results in a ::notice that claims a release was created and includes an empty $releaseURL, which is both misleading and relies on an uninitialized variable. Please gate the final notice so it only runs when a release has actually been created (e.g., in the non-WhatIf path where $releaseURL is set) and avoid referencing $releaseURL when it may be null.

---

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

[Copilot]

Pull request overview

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

---

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