CPAN versioning woes

Daniel Pfeiffer has asked for the wisdom of the Perl Monks concerning the following question:

For my script pl I recently bumped the version to reflect an end spurt towards 1.0. At the same time, I tried to remove the annoying v from the archive name. Sad result: CPAN is now stuck on v0.63.2. Even adding the v back again, doesn't make it reconsider. I asked PAUSE to reindex, to no avail. Nonetheless in the drop-down menu meta::cpan shows the correct order of versions. But it refuses to default to the latest. :-(

Applying the command PAUSE supposedly uses (my way: pl -oMExtUtils::MakeMaker 'e $_, MM->parse_version($_)' App-pl-*{2,0,1}/pl) I get a homogeneous progression of version numbers for my last three releases. This is also reflected in the bundled META files:

App-pl-v0.63.2/pl v0.63.2
App-pl-0.90.0/pl v0.90.0
App-pl-v0.90.1/pl v0.90.1

Side note, which will hopefully disapear with v1.0.0: Cpantesters even defaults to 0.57, as I was initially confused about versioning schemes. However it also says "App-pl v0.63.2 (latest distribution according to latest META file)" which is not true: App-pl v0.90.1's META files both say v0.90.1

What can I do to get out of this nightmare?

Comment on CPAN versioning woes

Replies are listed 'Best First'.
Re: CPAN versioning woes by choroba (Cardinal) on Jun 15, 2022 at 20:26 UTC
I noticed that when exploring the release metadata (click on MetaCPAN Explorer) for versions v0.63.2 and v0.90.1, the 63 says `"status" : "latest"`, while the 90 says `"status" : "cpan"`. I'm not sure what the precise interpretation is (MetaCPAN::Client::Release just lists the possible values, "latest", "cpan", and "backpan", but doesn't explain them). Did you get an email from Pause detailing the results of the indexing? It usually says whether there were any problems. Or maybe there were some problems on the server side and it needs several more days to catch up? `map{substr$_->[0],$_->[1]\|\|0,1}[\\|\|{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^ARGV,3]`	[reply] [d/l] [select]
Re^2: CPAN versioning woes by Daniel Pfeiffer (Acolyte) on Jun 15, 2022 at 21:04 UTC
OMG, yeah the email. Lost in spam folder. :-( You hit the nail on the head, thanks for the tip! Transferring the version to the dummy submodule broke in my release chain. Cpan refuses to consider what then looked like a decreasing version.	[reply]