Sign the dist as the last step before creating the archive. Take care not to modify/regenerate dist meta files or the manifest.

Error: Old SIGNATURE detected. Please inform the module author to regenerate SIGNATURE using Module::Signature version 0.82 or newer. gpg: Signature made Wed 28 May 2003 01:07:05 PM JST gpg: using DSA key B0A41D295AEFDD7C gpg: Can't check signature: No public key --- SIGNATURE Wed May 28 13:07:05 2003 +++ @@ -1,7 +1,7 @@ SHA1 ba294c77856a2df2c641ea9e42dcb6d2d5202f7b Build.PL SHA1 9082d01da49c30ddea12d4833f13e11bf8e13292 Changes SHA1 26ca11de757c98a437d7419d0c25a4d5caa02c74 MANIFEST -SHA1 c4cb19faaf03b2b179d918bca58e4386a5c75048 META.yml +SHA1 372cc411d11d5644bb11d2bf2672a2301d5585eb META.yml SHA1 f875a48340b43be10bc8d9da604aaeee607de110 Makefile.PL SHA1 77f58a79ceba75eceac3f53c58a971ef5e678c05 README SHA1 15e11b5e875c5eed63d0788e406d7666842a908d lib/CGI/Application/ValidateRM.pm ==> MISMATCHED content between SIGNATURE and distribution files! <==

If you are using Build.PL define the {requires}{perl} = VERSION field. If you are using MakeMaker (Makefile.PL) you should upgrade ExtUtils::MakeMaker to 6.48 and use MIN_PERL_VERSION parameter. Perl::MinimumVersion can help you determine which version of Perl your module needs.

Add a META.json to the distribution. Your buildtool should be able to autogenerate it.

Add 'use warnings' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.

Error: CGI::Application::ValidateRM

Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).

This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.