For the future, you can have a check in your author tests directory that checks that Changes contains a mention of the current version of the module.
I have such a test file in my template for distributions, but it relies on a Makefile.PL that is a modulino. Likely, the few modifications necessary to make it work in a general case:
#!perl -w use warnings; use strict; use File::Find; use Test::More tests => 2; =head1 PURPOSE This test ensures that the Changes file mentions the current version and that a release date is mentioned as well =cut #require './Makefile.PL'; ## Loaded from Makefile.PL #our %module = get_module_info(); my $module = 'Business::Stripe::WebCheckout'; (my $file = $module) =~ s!::!/!g; require "$file.pm"; my $version = sprintf '%0.2f', $module->VERSION; my $changes = do { local $/; open my $fh, 'Changes' or die $!; <$fh> } +; ok $changes =~ /^(.*$version.*)$/m, "We find version $version for $mod +ule"; my $changes_line = $1; ok $changes_line =~ /$version\s+20\d\d-[01]\d-[0123]\d\b/, "We find a +release date on the same line" or diag $changes_line;
In reply to Re: Module Change Log
by Corion
in thread Module Change Log
by Bod
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |