https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8298
--- Comment #4 from mar...@telka.sk --- Hi Sidney, Unfortunately, I do not know how exactly MetaCPAN works and where it gets the version info from so I can only guess. It looks like the version 4.000001 returned by the release/_search API endpoint comes from the 'main_module' which is Mail::SpamAssassin here: $ grep '4\.00' Mail-SpamAssassin-4.0.1/lib/Mail/SpamAssassin.pm our $VERSION = "4.000001"; # update after release (same format as perl $]) $ When I compare this to the podlators distribution where Pod::Man is listed as the 'main_module' then this assumption match: $ grep '6\.0\.2' podlators-v6.0.2/lib/Pod/Man.pm package Pod::Man v6.0.2; $ I assume the version '4.0.1' visible at https://metacpan.org/dist/Mail-SpamAssassin (for example in the 'Jump to version' drop down box) comes from the uploaded tarball file name - the tarball is Mail-SpamAssassin-4.0.1.tar.gz. And finally, the v4.0.1 version (with the leading 'v') comes very likely from the actual upload to CPAN/PAUSE step. I've never tried to upload anything to CPAN/PAUSE (please note that I'm not a Perl developer; I even do not have a PAUSE account), but I assume there is an entry for the version number you are just uploading and you simply put 'v4.0.1' there. -- You are receiving this mail because: You are the assignee for the bug.
