Publishing module using Sampler throws an error

[ykuijs]

Problem description

The pipeline of my module throws an error since this week. I suspect this is caused by v0.118.2 of Sampler:

Verbose logs

About to release '/home/runner/work/M365DSC.CompositeResources/M365DSC.CompositeResources/output/M365DSC.CompositeResources/1.25.122.100'.
  Outputting configured repositories using command Get-PSResourceRepository

Name      Uri                                      Trusted Priority
----      ---                                      ------- --------
PSGallery https://www.powershellgallery.com/api/v2 False   50
  Publishing using command Publish-PSResource
ERROR: Error occured while running 'Test-ModuleManifest': Object reference not set to an instance of an object.
At /home/runner/work/M365DSC.CompositeResources/M365DSC.CompositeResources/output/RequiredModules/Sampler/0.118.2/tasks/release.module.build.ps1:389 char:13
+             Publish-PSResource @PublishModuleParams
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
At /home/runner/work/M365DSC.CompositeResources/M365DSC.CompositeResources/output/RequiredModules/Sampler/0.118.2/tasks/release.module.build.ps1:339 char:1
+ task publish_module_to_gallery -if ($GalleryApiToken -and (Get-Comman …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Build FAILED. 2 tasks, 1 errors, 0 warnings 00:00:02.1522950
Publish-PSResource: /home/runner/work/M365DSC.CompositeResources/M365DSC.CompositeResources/output/RequiredModules/Sampler/0.118.2/tasks/release.module.build.ps1:389

How to reproduce

Not sure

Expected behavior

Successful publication of the module.

Current behavior

Throws an error message

Suggested solution

Do not know the root cause

Operating system the target node is running

Ubuntu
  24.04.1
  LTS

PowerShell version and build the target node is running

PSv7 as part of Build image

Module version used

Most recent (0.118.2)

[ykuijs]

When locking the version of Sampler to v0.118.1, my module is published just fine. So a change in v0.118.2 is causing this issue. Any ideas/suggestions?

[johlju]

There were a problem in Azure DevOps build agent that prevented DSC Community repos from publish modules. Probably due to missing PowerShellGet. The change was made that if Microsoft.PowerShell.PSResourceGet is present it will use Publish-PSResource, if it is not it will use Publish-Module from PowerShellGet.

My hope was that we could move away from PowerShellGet.

A quick solution would be to remove Microsoft.PowerShell.PSResourceGet from your $PSModulePath and the old behavior should kick in.

But more interesting is why your module cannot be deploy using Publish-PSResource? 🤔

[gaelcolas]

I'm closing this one because we've had this task working for a while, and I agree that if anything we're trying to move away from PowerShellGet.

Soon we'll be able to pack without using PowerShellGet, and I'll start removing the hard dependency on PowerShellGet (because you can't import PSResourceGet if PowerShellGet is already loaded... :/