`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.