[0.9.0-rc1] Install-PSResource install latest prerelease even without '-Prerelease'. Repository: GitLab

[Kj3l]

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.

Steps to reproduce

These packages has been published using 'Publish-PSResource' on a GitLab package registry.

• MyModule version '1.0.0' ( last stable )
• MyModule version '1.1.0-dev' ( with prerelease property in manifest )

Install-PSResource 'MyModule'

It will install the prerelease version (1.1.0-dev) in the last stable version folder (1.0.0), which cause the module impossible to import (version does not match).

Other test works fine:

Install-PSResource 'MyModule' -Version '1.0.0'

Install version 1.0.0 correctly.

Install-PSResource 'MyModule' -Prerelease

Install version 1.1.0-dev correctly.

Expected behavior

'MyModule' version *1.0.0* is installed in version folder : "..PowerShell\Modules\MyModule\1.0.0\"

Actual behavior

'MyModule' version *1.1.0-dev* is installed in version folder : "..PowerShell\Modules\MyModule\1.0.0\"

Error details

VERBOSE: Skipping the Version folder 1.0.0 under Module C:\..\PowerShell\Modules\MyModule as it does not have a valid module manifest file.
Import-Module: The specified module 'C:\..\PowerShell\Modules\MyModule \' was not loaded because no valid module file was found in any module directory.

Environment data

ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Binary     0.9.0      rc1        Microsoft.PowerShell.PSResourceGet  {Find-PSResource, Get-InstalledPSResource, Get-PSResourceRepository, Get-PSScriptFileInfo…}

Key   : PSVersion
Value : 7.3.4
Name  : PSVersion


Key   : PSEdition
Value : Core
Name  : PSEdition


Key   : GitCommitId
Value : 7.3.4
Name  : GitCommitId


Key   : OS
Value : Microsoft Windows 10.0.19045
Name  : OS


Key   : Platform
Value : Win32NT
Name  : Platform


Key   : PSCompatibleVersions
Value : {1.0, 2.0, 3.0, 4.0…}
Name  : PSCompatibleVersions


Key   : PSRemotingProtocolVersion
Value : 2.3
Name  : PSRemotingProtocolVersion


Key   : SerializationVersion
Value : 1.1.0.1
Name  : SerializationVersion


Key   : WSManStackVersion
Value : 3.0
Name  : WSManStackVersion

Visuals

No response

[SydneyhSmith]

Thanks @Kj3l could you share Get-PSResourceRepository <reponame> | fl taking out any sensitive data you don't want to share?

[Kj3l]

I use the project-level NuGet endpoint.

Get-PSResourceRepository -Name GitLab | fl *

Name           : GitLab
Uri            : https://git.apps.mycompany.com/api/v4/projects/7636/packages/nuget/index.json
Trusted        : True
Priority       : 50
CredentialInfo :
ApiVersion     : v3

[SydneyhSmith]

Thanks @Kj3l we need to look at the GitLab api's closer to determine how they may be treating Prerelease tags slightly differently than other types of v3 repos we support-- in their docs we noticed they also support v2 feeds-- though in general v3 is probably better you may want to try v2 to see if this resolves the issue

[Kj3l]

I couldn't get a v2 to work.

I think the request filter is not working correctly with GitLab.
I've published a 'new' module version 0.9.0 to test my idea, and now this one installs (instead of 1.0.0)

It installs the latest published package by date but not by version.

As a workaround, I search for all versions, sort them and install the last one.

$param = Find-PSResource -Name MyModule -Version * -Repository GitLab | Sort-Object { [version] $_.Version } | Select-Object -Last 1
Install-PSResource @param -Reinstall -Scope AllUsers