badges / badges/shields

PowerShellGallery: PreRelease version not working

Open
#2,800 2 comments 0 reactions 0 assignees View on GitHub
question
Dominant language
JavaScript
Stars
27.2k
Forks
5.6k
Avg merge
1d 8h
Merged PRs (30d)
46

Description

Are you experiencing an issue with...

- [x] [shields.io](https://shields.io/#/)
- [ ] My own instance
- [ ] [gh-badges NPM package](https://www.npmjs.com/package/gh-badges)

:beetle: **Description**

I've recently published some PowerShell Module prereleases and tried to create the badges.
Unfortunately it returns ``not found.` So I looked into the examples an tried the following prerelease version syntax:

- 1.2.5-alpha1
- 1.5.6.-preview (same syntax like the example Azure.Storage ( AzureRM.Batch has currently a preview version))

Am I using the wrong version syntax for PreReleases?

> PowerShellGallery requires a syntax like this in general: `Major.Minor.Fix-PreReleaseString` for PreReleases

:link: **Link to the badge**

- ![](https://img.shields.io/powershellgallery/vpre/PSCoverage.svg) -> `PSCoverage`
- ![](https://img.shields.io/powershellgallery/vpre/PSCredentialStore.svg) ->`PSCredentialStore`
- ![](https://img.shields.io/powershellgallery/vpre/apvr-test.svg) -> `apvr-test`

:bulb: **Possible Solution**

Contributor guide

Open the contributing guide

Research direction

Start by requesting the three linked PowerShell Gallery vpre badge URLs and comparing their results with the corresponding prerelease package versions. Determine whether the reported version forms are accepted, and consider the issue done when valid PowerShell Gallery prereleases resolve to badges instead of "not found."

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.