Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: PSModule/Publish-PSModule
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1
Choose a base ref
...
head repository: PSModule/Publish-PSModule
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.0.0
Choose a head ref
  • 1 commit
  • 18 files changed
  • 1 contributor

Commits on Apr 17, 2025

  1. 🌟 [Major]: Using settings from Process-PSModule + common dependenci… 

    …es (#49)

## Description

This update elevates `Publish-PSModule` to `v2`, refactoring its inputs,
scripts, and workflows for improved modularity, clarity, and security,
and syncs its usage within the `Process‑PSModule` workflow to consume
the new version and centralized settings.

PSModule/Process-PSModule/pulls/150

### Key Updates

- Explicit Inputs & Defaults
Removed the legacy `ConfigurationFile` input in favor of clearly defined
action inputs (including a new `WorkingDirectory` defaulting to `'.'`),
with reordered parameters for consistency, changing its usage to be via
the settings file introduced in Process-PSModule.
- Bug Fix & Logging Enhancements
Fixed the extra “v” prefix in the Gallery comment by sanitizing the
version string, and added comprehensive logging of all inputs at script
start to aid diagnostics.
  - Fixes PSModule/Process-PSModule/issues/82
- Moved helper scripts
Extracted `Convert-VersionSpec` and `Resolve-PSModuleDependency` into
standalone helpers in `Install-PSModuleHelpers`, replaced verbose calls
with `Write-Host`, and strengthened retry/null‑check logic when querying
the PowerShell Gallery.
- Workflow Security & Consistency
Updated test workflows to use the repository workspace path uniformly
and removed the hardcoded `GITHUB_TOKEN` from the Auto‑Release workflow
in favor of `${{ github.token }}`.

## Type of change

<!-- Use the check-boxes [x] on the options that are relevant. -->

- [ ] 📖 [Docs]
- [ ] 🪲 [Fix]
- [ ] 🩹 [Patch]
- [ ] ⚠️ [Security fix]
- [ ] 🚀 [Feature]
- [x] 🌟 [Breaking change]

## Checklist

<!-- Use the check-boxes [x] on the options that are relevant. -->

- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
    @MariusStorhaug
    MariusStorhaug authored Apr 17, 2025
    Configuration menu
    Copy the full SHA
    2da4e21 View commit details
    Browse the repository at this point in the history
Loading