Releases: PSModule/PSMA
Releases · PSModule/PSMA
Release list
v0.0.1
Move framework actions into per-action folders (as-is) (#1)
Summary
First step of the PSMA consolidation (PSModule/Process-PSModule#384): fold the framework-internal GitHub Actions into one repo, one folder per action, moved as-is.
Each action keeps its own action.yml + src/scripts + tests, so every action stays independently usable as PSModule/PSMA/<Action>@<ref> while we migrate. No logic changed in this PR — it only relocates the actions.
Folders added
Build-PSModule/Test-PSModule/Publish-PSModule/Get-PSModuleSettings/Resolve-PSModuleVersion/(usesscripts/)Install-PSModuleHelpers/Document-PSModule/Get-PesterCodeCoverage/Get-PesterTestResults/
Copied per action: action.yml, the script dir (src/scripts), tests/, README.md. Skipped each source repo's .github/ (its own CI), LICENSE (repo root already has one), and dotfiles. The Template-Action root scaffolding is left untouched for now.
Next steps (separate PRs)
- Move any inline
action.ymllogic into the PowerShell scripts (most actions already just call a main script). - Consolidate shared functions into a common
PSMAmodule imported by a new rootmain.ps1that dispatches on an activity input (e.g.main.ps1 Build,main.ps1 TestLocal), then re-point the Process-PSModule sub-workflows at PSMA.
Tracking: PSModule/Process-PSModule#384