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 23 Jun 2003 10:39:52 AM JST gpg: using DSA key B0A41D295AEFDD7C gpg: Can't check signature: No public key --- SIGNATURE Mon Jun 23 10:39:52 2003 +++ @@ -1,7 +1,7 @@ SHA1 ba294c77856a2df2c641ea9e42dcb6d2d5202f7b Build.PL SHA1 7d3cd446437e78af7880199ae3692b239d348139 Changes SHA1 26ca11de757c98a437d7419d0c25a4d5caa02c74 MANIFEST -SHA1 eb11027587a57eb0737e956b6a14cc3b97d09864 META.yml +SHA1 eb8c14171a689781c3cb3c3e4f90a857f5d9f978 META.yml SHA1 f875a48340b43be10bc8d9da604aaeee607de110 Makefile.PL SHA1 19400632fca22d9840b4dcaa47a594ac336b4ec7 README SHA1 3d0b621776af0f722ee4f01bc12b5de559ad4a67 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.