5.27.0 contained 5.20170531; 5.27.1 contained 5.20170621
authorSteve Hay <steve.m.hay@googlemail.com>
Thu, 29 Jun 2017 17:07:55 +0000 (18:07 +0100)
committerSteve Hay <steve.m.hay@googlemail.com>
Thu, 29 Jun 2017 17:07:55 +0000 (18:07 +0100)
The 5.27.0 data was correct until commit a6b08d8b5d, which wrongly updated
it to 5.20170620 instead of adding 5.27.1 stubs saying that.
That mistake was perhaps the reason that 5.27.1 ended up containing
5.20170621 rather than the expected 5.20170620?

dist/Module-CoreList/Changes
dist/Module-CoreList/lib/Module/CoreList.pm

index 57f333b..4aabd52 100644 (file)
@@ -1,7 +1,7 @@
 5.20170720
   - Updated for v5.27.2
 
-5.20170620
+5.20170621
   - Updated for v5.27.1
 
 5.20170531
index 17c2026..58b4330 100644 (file)
@@ -14112,9 +14112,9 @@ for my $version ( sort { $a <=> $b } keys %released ) {
             'B::Deparse'            => '1.41',
             'B::Op_private'         => '5.027000',
             'Config'                => '5.027',
-            'Module::CoreList'      => '5.20170620',
-            'Module::CoreList::TieHashDelta'=> '5.20170620',
-            'Module::CoreList::Utils'=> '5.20170620',
+            'Module::CoreList'      => '5.20170531',
+            'Module::CoreList::TieHashDelta'=> '5.20170531',
+            'Module::CoreList::Utils'=> '5.20170531',
             'O'                     => '1.02',
             'attributes'            => '0.3',
             'feature'               => '1.48',