What’s New
The headline features of each ModuleForge release. Every release, including prereleases, has full, automatically generated release notes on the GitHub releases page, built from its commit messages.
1.4 (November 2026)
Pinned, predictable builds
BuildDependencies.psd1pins the modules your pipelines install: ModuleForge, Pester, PSScriptAnalyzer and PlatyPS. Each pipeline installs and imports exactly the pinned version. See Build Dependencies.testDependenciesdecides what the Pester pipelines install. Tests never install ModuleForge.- Build and Release, and PSGallery Release, can install the pinned ModuleForge, or the latest from PSGallery, with
dependency_source.
Checking what you ship
- Build Test, an optional workflow or pipeline, installs the module you just published and checks it exports exactly what your source declares. See Testing the Published Module.
- Project Rules runs your own PSScriptAnalyzer rules as an advisory pass with its own pull request comment.
Add-MFProjectRulesadds two ready-made rule sets: Constrained Language Mode compatibility, and help examples. See Project Rules. Get-MFBuildSummaryreports a build’s version, exports, size and SHA256 hashes, and Build and Release shows it on the run.
Easier setup
New-MFProject -Scaffold GitHub,AzureDevOpsadds the CI scaffold in the same step.New-MFProjectfills inLicenseUrifrom yourLICENSEfile for GitHub and Azure DevOps projects.Get-MFGitPrefixHelplists the commit prefixes from the command line.- Azure DevOps pipelines work with project- or organization-scoped feeds, and warn rather than fail when a project can’t publish code coverage.
Under the hood
- Manifests list exported aliases by name, never
*. Aliases from[Alias()], and fromSet-AliasorNew-Aliaswith a literal name, are included. - Hardened pipelines. Pull request code runs without a write token, comments are posted by jobs that never run it, and tokens stay off disk. See CI Security Model.
- Docs are generated with Microsoft.PowerShell.PlatyPS 1.0, replacing the unmaintained platyPS 0.14.
- Minimum PowerShell 7.6 LTS and Pester 6.
Upgrading from 1.3
- PowerShell 7.6 and Pester 6 are now required, for ModuleForge itself and for the pipelines.
- Get the new templates by running
Add-MFGithubScaffoldorAdd-MFAzureDevOpsScaffoldagain. Without-Forceit only adds files you don’t have, such asBuildDependencies.psd1, the new scripts and the.exampletemplates. With-Forceit overwrites your workflows, and resetsBuildDependencies.psd1to its default pins. See the upgrade FAQ. - Aliases are now exported by name. An alias whose name is a variable, such as
Set-Alias -Name $name ..., can’t be listed, and the build warns that it won’t be exported. Use a literal name, or[Alias()]on the function. - PSGallery Release’s input changed from
moduleforge_release_toggletodependency_source. See the PSGallery tutorial.
1.3 (June 2026)
- Build provenance. Built modules record the ModuleForge version and hashes that produced them, in the
.psm1header and manifest. - Private functions are linted and covered. PSScriptAnalyzer and code coverage include
source/private, and a roottestsfolder is supported. Invoke-MFPester.ps1runs Pester locally the same way the pull request pipeline does.Invoke-MFBuildPreReleasebuilds a prerelease locally.Resolve-MFModuleCasefixes the lowercase install folders NuGet feeds can cause on Linux and macOS.Write-MFModuleDocsgenerates a Just the Docs site, with navigation, from your help.
1.2 (July 2025)
- Azure DevOps support, with
Add-MFAzureDevOpsScaffold, alongsideAdd-MFGithubScaffold. - Changelogs from commit messages, with
Get-MFGitChangeLog, added to each release and its manifest. - Versions from git tags, with
Get-MFGitLatestVersionandGet-MFNextSemver. Write-MFModuleDocsfor function reference docs and a changelog on GitHub Pages.