Tags prefixed with 'v' seem to confuse composer metadata

[craigrileyuk]

Pricore Version

0.52.4

PHP Version

Whatever's in the docker image

Description

Certain packages seem to be confusing Composer when running outdated. I tend to tag with a 'v' prefix and when fetching metadata from my Pricore instance, this seems to double up the tags and make it claim there are updates available when there aren't.

Steps to Reproduce

1. Sync a repo which uses 'v' prefixes in tags
2. Run composer outdated when on the latest version of your package.
3. Output shows update available: evo-mark/evo-laravel-profanity [current] 1.2.0 [available] 1.2.0

Expected Behavior

No updates should be available for packages at their latest version.

Actual Behavior

composer outdated shows update available in red (patch or minor release available - update recommended)

Additional Context

Output of composer show --latest -vvv

name     : evo-mark/evo-laravel-profanity
descrip. : Use Pest's profanity wordlist in your validator
keywords : censor, cursing, evo-mark, expletives, filter, laravel, pest, profanity, swearing
versions : * v1.2.0
released : 2026-03-20, 2 months ago
latest   : 1.2.0 released 2026-05-04, 4 weeks ago
type     : library
license  : MIT License (MIT) (OSI approved) https://spdx.org/licenses/MIT.html#licenseText
homepage : https://github.com/evo-mark/evo-laravel-profanity
source   : [git] https://github.com/evo-mark/evo-laravel-profanity.git
dist     : [zip] https://api.github.com/repos/evo-mark/evo-laravel-profanity/zipball
path     : /some-path/evo-mark/evo-laravel-profanity
names    : evo-mark/evo-laravel-profanity

Output of composer show --all

versions : * 1.2.0, * v1.2.0, 1.1.1, 1.1.0, 1.0.1, 1.0.0, dev-main

Synced repo tags:

https://github.com/evo-mark/evo-laravel-profanity/tags

[maartenbode]

Should be fixed in #159!