All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
- Bump Pester to latest 5.6.1
- #52 Pester object wasn't being passed back after running tests, causing the Pester task to never fail (via @webtroter)
- #55 Add
-Module
parameter toBuild-PSBuildUpdatableHelp
(via @IMJLA) - #60 Fix Windows
PowerShell compatibility in
Initialize-PSBuild
(via @joshooaj) - #62 Fix code coverage output fle format not working (via @OpsM0nkey)
- Fixed bug in IB task
GenerateMarkdown
when dot sourcing precondition
- #50 Invoke-Build tasks brought inline with psake equivalents (via @JustinGrote)
- New code coverage parameters for setting output path and format:
$PSBPreference.Test.CodeCoverage.OutputFile
- Output file path for code coverage results$PSBPreference.Test.CodeCoverage.OutputFileFormat
- Code coverage output format
-
When "compiling" a monolithic PSM1, add support for both inserting headers/footers for the entire PSM1, and for each script file. Control these via the following new build parameters (via @pauby)
$PSBPreference.Build.CompileHeader
$PSBPreference.Build.CompileFooter
$PSBPreference.Build.CompileScriptHeader
$PSBPreference.Build.CompileScriptFooter
-
Add ability to import project module from output directory prior to executing Pester tests. Toggle this with
$PSBPreference.Test.ImportModule
. Defaults to$false
. (via @joeypiccola) -
Use
$PSBPreference.Build.CompileDirectories
to control directories who's contents will be concatenated into the PSM1 when$PSBPreference.Build.CompileModule
is$true
. Defaults to@('Enum', 'Classes', 'Private', 'Public')
. -
Use
$PSBPreference.Build.CopyDirectories
to control directories that will be copied "as is" into the built module. Default is an empty array.
-
$PSBPreference.Build.Exclude
now should be a list of regex expressions when$PSBPreference.Build.CompileModule
is$false
(default). -
Use Pester v5
-
Overriding
$PSBPreference.Build.OutDir
now correctly determines the final module output directory.$PSBPreference.Build.ModuleOutDir
is now computed internally and SHOULD NOT BE SET DIRECTLY.$PSBPreference.Build.OutDir
will accept both relative and fully-qualified paths. -
Before, when
$PSBPreference.Build.CompileModule
was set to$true
, any files listed in$PSBPreference.Build.Exclude
weren't being excluded like they should have been. Now, when it is$true
, files matching regex expressions in$PSBPreference.Build.Exclude
will be properly excluded (via @pauby) -
$PSBPreference.Help.DefaultLocale
now defaults toen-US
on Linux since it is not correctly determined withGet-UICulture
.
- Allow using both
Credential
andApiKey
when publishing a module (via @pauby)
- Don't overwrite Pester parameters when specifying
OutputPath
orOutputFormat
(via @ChrisLGardner)
- Don't create module page MD file.
- #19 Allow the
BHBuildOutput
environment variable defined byBuildHelpers
to be set via the$PSBPreference.Build.ModuleOutDir
property of the build tasks (via @pauby)
- Refactor build properties into a single hashtable
$PSBPreference
- #11 The Invoke-Build tasks are now auto-generated from the psake tasks via a converter script (via @JustinGrote)
- Add
Publish
task to publish the module to the defined PowerShell Repository (PSGallery by default).
- #4 Fix syntax for
Analyze
task inIB.tasks.ps1
(via @nightroman)
- Initial commit