v0.118.0-preview0003
Pre-release
Pre-release
[v0.118.0-preview0003]
Changed
- Update template for SECURITY.md and add it to Sampler repository as well.
- Built module is now built in a separate folder. This is to split the paths
for the built module and all required modules, to avoid returning duplicate
modules when usingGet-Module -ListAvailable
. The templates already has
this configuration. - Now PSResourceGet always default to the latest released version if no
specific version is configured or passed as parameter. - Templates was changed to use PSResourceGet as the default method
of resolving dependencies. It is possible to change to the method
PowerShellGet & PSDepend by changing the configuration. Also default to
using PowerShellGet v3 which is a compatibility module that is a wrapper
for the equivalent command in PSResourceGet. - Switch to build worker
windows-latest
for the build phase of the pipeline
due to a issue usingPublish-Module
on the latest updated build worker in
Azure Pipelines.
Fixed
- Now the tasks work when using
Set-SamplerTaskVariable
with tasks that
do not have the parameterChocolateyBuildOutput
. - Remove duplicate SECURITY.md template files, and fix templates to
point to the single version. - Correct description of the parameter
GalleryApiToken
in the build task
script release.module.build.ps1. Fixes #442 - ModuleFast now supports resolving individual pre-release dependencies
that is part of RequiredModules.psd1. It is also possible to specify
NuGet version ranges
in RequiredModules.psd1, although then the file is not compatible with
PSResourceGet or PSDepend (so no fallback can happen). - Now it won't import legacy PowerShellGet and PackageManagement when
PSResourceGet or ModuleFast is used. - Now it works saving PowerShellGet compatibility module when configured.
- Now if both ModuleFast and PowerShellGet compatibility module is configured
PSResourceGet is automatically added as a dependency. This is for example
needed for publishing built module to the gallery.