PowerShell / PowerShell/PSResourceGet

[Question] Publish-PsResource and the versioning of a module manifest

Open
#1,346 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Docs Area-Publish Needs-Attention :wave:
Dominant language
C#
Stars
576
Forks
114
Avg merge
1d 2h
Merged PRs (30d)
7

Description

Question

For a local repository Publish-PSResource must it respect the versioning indicated in this doc ?

With Microsoft.PowerShell.PSResourceGet v0.5.23 this is not the case :

Get-PSResourceRepository

Name        Uri                                                      Trusted Priority
----        ---                                                      ------- --------
PSGallery   https://www.powershellgallery.com/api/v2                 False   50
PSRepoLocal file:///C:/Users/Laurent/AppData/Local/Temp/PSRepoLocal/ True    50


Publish-PSResource -Path C:\Temp\Gallery\String\1.1.0.1 -Repository PSRepoLocal -verbose
#ok no error

dir C:\Users\Laurent\AppData\Local\Temp\PSRepoLocal


    Répertoire : C:\Users\Laurent\AppData\Local\Temp\PSRepoLocal


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----        07/08/2023     13:52          10669 String.1.1.0--beta.nupkg
-a----        07/08/2023     12:17           8885 String.1.1.0-prerelease.nupkg
-a----        07/08/2023     12:18           8889 String.1.1.0.1-prerelease.nupkg

NOTE :
If I use Publish-Module and Publish-PSResource for the same local repository, with Install-Module I cannot install modules that do not respect versioning :
image

But Find-Module considering in the result the packages which do not respect versioning :
image

Proposed technical implementation details (optional)

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the shown Publish-PSResource, Find-Module, and Install-Module commands against the local PSRepoLocal repository, then compare their handling of the module manifest version with the linked prerelease-versioning documentation. Done means the behavior for published, discoverable, and installable packages is consistent with the documented versioning rules.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
cli, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.