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 Mon 21 Apr 2003 07:22:47 AM JST gpg: using DSA key B0A41D295AEFDD7C gpg: Can't check signature: No public key --- SIGNATURE Mon Apr 21 07:22:47 2003 +++ @@ -1,7 +1,7 @@ SHA1 0909c0ebd00e819914abcc9280e2f4086db85026 Build.PL SHA1 3967ab0066e1564dd3cfe201fa13bd4729158739 Changes SHA1 09580ce342db1c0b6b7686d93af338ca54a6298f MANIFEST -SHA1 1513f183f2f7fe2eff9736dc1ed5927d493119a6 META.yml +SHA1 13d103845f0e82eb55b1f3986c2c11cd57a3a2ee META.yml SHA1 3881837767c85ffc51f01f9fbd9bc561768d1cc1 Makefile.PL SHA1 f1d417c48b435f2f9658d1d12356c3d19a04b036 lib/CGI/Application/ValidateRM.pm SHA1 8da06dbb05c562e1720e2e75ab3a25641cef58f1 t/01_basic.t ==> 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.