`Update-PSResource` Won't Update New `PreRelease` Version With Same `Version`

[mattcargile]

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

udres PSParseHtml -pre

Expected behavior

Should update from `preview3` to `preview4` on version `2.0.0`.

Actual behavior

VERBOSE: Installed package PSParseHTML 2.0.0 is already up to date.

Error details

No Error

Environment data

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


Name                           Value
----                           -----
PSVersion                      7.5.2
PSEdition                      Core
GitCommitId                    7.5.2
OS                             Microsoft Windows 10.0.22631
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visuals

N/A

EDIT 1

Maybe the pattern for this type of flow is an uninstall and install because it can't update the folder in-line so to speak. udres -force won't work either.

[kilasuit]

Did you use -force at all?

I recall this was required in the PowerShellGet implementations and may be needed in this too

[mattcargile]

Did you use -force at all?

I recall this was required in the PowerShellGet implementations and may be needed in this too

Just tried -force, it doesn't work. I did edit my post as I assume this workflow isn't possible and you'd have to uninstall and install. I assume this is because the folder path doesn't include the PreRelease portion of the version.

[kilasuit]

Is the module you are trying to update loaded in the session

if so try in a -noProfile session with & without -force

[mattcargile]

It isn't loaded in the current session. I assume this output is the issue where the Versions match.

[o-l-a-v]

Some more info with -Debug -Verbose:

PS > Update-PSResource -Repository PSGallery -TrustRepository -Scope CurrentUser -Name 'PSParseHtml' -Prerelease -Verbose -Debug

VERBOSE: All paths to search: 'C:\Users\<redacted>\Documents\PowerShell\Modules'
VERBOSE: All paths to search: 'C:\Users\<redacted>\Documents\PowerShell\Scripts'
VERBOSE: Retrieving directories in the path 'C:\Users\<redacted>\Documents\PowerShell\Modules'
VERBOSE: Retrieving directories in the path 'C:\Users\<redacted>\Documents\PowerShell\Scripts'
VERBOSE: All paths to search: 'C:\Users\<redacted>\Documents\PowerShell\Modules\Microsoft.PowerToys.Configure'
VERBOSE: All paths to search: 'C:\Users\<redacted>\Documents\PowerShell\Modules\PSParseHTML'
VERBOSE: All paths to search: 'C:\Users\<redacted>\Documents\PowerShell\Modules\testmodule99'
DEBUG: In GetHelper::GetPackagesFromPath()
DEBUG: In GetHelper::FilterPkgPathsByName()
DEBUG: In GetHelper::FilterPkgPathsByVersion()
DEBUG: Searching through package path: 'C:\Users\<redacted>\Documents\PowerShell\Modules\PSParseHTML'
DEBUG: Searching through package path: 'C:\Users\<redacted>\Documents\PowerShell\Modules\PSParseHTML'
DEBUG: Searching through package version path: 'C:\Users\<redacted>\Documents\PowerShell\Modules\PSParseHTML\2.0.0'
DEBUG: Package version parsed as NuGet version: '2.0.0-Preview3'
DEBUG: Reading package metadata from: 'C:\Users\<redacted>\Documents\PowerShell\Modules\PSParseHTML\2.0.0\PSGetModuleInfo.xml'
DEBUG: In FindHelper::FindByResourceName()
DEBUG: Parameters passed in >>> Name: 'PSParseHTML'; ResourceType: 'None'; VersionRange: ''; NuGetVersion: ''; VersionType: 'NoVersion'; Version: ''; Prerelease: 'True'; Tag: ''; Repository: 'PSGallery'; IncludeDependencies 'True'
DEBUG: Searching through repository 'PSGallery'
DEBUG: In FindHelper::SearchByNames()
DEBUG: No version specified, package name is specified
DEBUG: In V2ServerAPICalls::FindName()
DEBUG: In V2ServerAPICalls::HttpRequestCall()
DEBUG: Request url is 'https://www.powershellgallery.com/api/v2/FindPackagesById()?%24filter=Id+eq+%27PSParseHTML%27+and+IsAbsoluteLatestVersion+eq+true&%24inlinecount=allpages&id=%27PSParseHTML%27'
DEBUG: Found package 'PSParseHTML' version '2.0.0'
DEBUG: Package 'PSParseHTML' returned from server
DEBUG: Package 'PSParseHTML' was previously discovered and returned
DEBUG: Finding dependency packages for 'PSParseHTML'
DEBUG: Formatted full package version is: '2.0.0-Preview4'
VERBOSE: Installed package PSParseHTML 2.0.0 is already up to date.

PS >

So it reads installed version as 2.0.0-Preview3 and the newest available prerelease version as 2.0.0-Preview4. 🤔

[gwojan]

Some more info with -Debug -Verbose:

PS > Update-PSResource -Repository PSGallery -TrustRepository -Scope CurrentUser -Name 'PSParseHtml' -Prerelease -Verbose -Debug

VERBOSE: All paths to search: 'C:\Users<redacted>\Documents\PowerShell\Modules'
VERBOSE: All paths to search: 'C:\Users<redacted>\Documents\PowerShell\Scripts'
VERBOSE: Retrieving directories in the path 'C:\Users<redacted>\Documents\PowerShell\Modules'
VERBOSE: Retrieving directories in the path 'C:\Users<redacted>\Documents\PowerShell\Scripts'
VERBOSE: All paths to search: 'C:\Users<redacted>\Documents\PowerShell\Modules\Microsoft.PowerToys.Configure'
VERBOSE: All paths to search: 'C:\Users<redacted>\Documents\PowerShell\Modules\PSParseHTML'
VERBOSE: All paths to search: 'C:\Users<redacted>\Documents\PowerShell\Modules\testmodule99'
DEBUG: In GetHelper::GetPackagesFromPath()
DEBUG: In GetHelper::FilterPkgPathsByName()
DEBUG: In GetHelper::FilterPkgPathsByVersion()
DEBUG: Searching through package path: 'C:\Users<redacted>\Documents\PowerShell\Modules\PSParseHTML'
DEBUG: Searching through package path: 'C:\Users<redacted>\Documents\PowerShell\Modules\PSParseHTML'
DEBUG: Searching through package version path: 'C:\Users<redacted>\Documents\PowerShell\Modules\PSParseHTML\2.0.0'
DEBUG: Package version parsed as NuGet version: '2.0.0-Preview3'
DEBUG: Reading package metadata from: 'C:\Users<redacted>\Documents\PowerShell\Modules\PSParseHTML\2.0.0\PSGetModuleInfo.xml'
DEBUG: In FindHelper::FindByResourceName()
DEBUG: Parameters passed in >>> Name: 'PSParseHTML'; ResourceType: 'None'; VersionRange: ''; NuGetVersion: ''; VersionType: 'NoVersion'; Version: ''; Prerelease: 'True'; Tag: ''; Repository: 'PSGallery'; IncludeDependencies 'True'
DEBUG: Searching through repository 'PSGallery'
DEBUG: In FindHelper::SearchByNames()
DEBUG: No version specified, package name is specified
DEBUG: In V2ServerAPICalls::FindName()
DEBUG: In V2ServerAPICalls::HttpRequestCall()
DEBUG: Request url is 'https://www.powershellgallery.com/api/v2/FindPackagesById()?%24filter=Id+eq+%27PSParseHTML%27+and+IsAbsoluteLatestVersion+eq+true&%24inlinecount=allpages&id=%27PSParseHTML%27'
DEBUG: Found package 'PSParseHTML' version '2.0.0'
DEBUG: Package 'PSParseHTML' returned from server
DEBUG: Package 'PSParseHTML' was previously discovered and returned
DEBUG: Finding dependency packages for 'PSParseHTML'
DEBUG: Formatted full package version is: '2.0.0-Preview4'
VERBOSE: Installed package PSParseHTML 2.0.0 is already up to date.

PS >
So it reads installed version as 2.0.0-Preview3 and the newest available prerelease version as 2.0.0-Preview4. 🤔

This wouldn't be an issue if PSResourceGet supported semantic versioning. 😉 In the mean time bumping the build version to match the ordinal of the preview version would be an acceptable workaround. This is how it's being done for PSReadLine beta releases. For example:

1.2.0-preview2 --> 1.2.2
1.2.0-preview3 --> 1.2.3

[mattcargile]

This was completed?!