Publish-Module, Save-Module and Install-Module do not work with pre-release module, which depends on another pre-release module about psresourceget

[SteveL-MSFT]

I agree that AllowPrerelease should be propagated to other calls once specified by the user or if they specify a specific version string that includes prerelease. Note that a stable module that depends on prerelease dependencies is not a pattern we want to support so that should continue to fail.

[kumbham]

@SydneyhSmith @kamennikolov I ran into a similar issue where I'm trying to publish a module that depends on a pre-release version of another module. Publish-Module throws No match was found for the specified search criteria and module name .. error. Are there any workarounds to resolve this problem?

[kamennikolov]

@kumbham we fixed Publish-Module locally and managed to upload.

[kumbham]

@kamennikolov thanks for the response. Do you mind sharing me few pointers on where and how can I fix it?

[dmilov]

@kamennikolov thanks for the response. Do you mind sharing me few pointers on where and how can I fix it?

It was back in 2018. We used PowerShellGet 1.6 then. The problem was in the ValidateAndGet-RequiredModuleDetails function of PSModule.psm1

The fix we did locally to be able to publish the prerelease modules was at line 8607 of PSModule.psm1 which calls Find-Module with splatting @FindModuleArguments. The FindModuleArguments hashble is defined 3 lines above at 8604 and the only parameter in it is the Name of the module. That is breaking the validation. -AllowPrerelease has to be specified on the Find-Module to be able to discover the published prerelease module dependencies.

The fix I did then was to replace

Find-Module @FindModuleArguments

with

Find-Module -Name $ModuleName -AllowPrerelease

another option is to add AllowPrerelease key with $true in the FindModuleArguments hashtable

The fix shouldn't have affect non prerelease modules it should work for them as well.

[TanmayDharmaraj]

A similar issue arises when I perform Save-Module as well.

[SteveL-MSFT]

This is fixed via beta10

[darksidemilk]

Is there any chance of this fix being added as a patch to 2.x ?
I realized that there's been a stop on development and whatnot, but it would be very helpful in our migration path to powershellget 3 and powershell 7 if we could handle these preRelease depdendencies on our current modules.