5.27.0 contained 5.20170531; 5.27.1 contained 5.20170621

The 5.27.0 data was correct until commit a6b08d8, 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?

Author: steve-m-hay

dist/Module-CoreList/Changes

@@ -1,7 +1,7 @@
 5.20170720
   - Updated for v5.27.2
 
-5.20170620
+5.20170621
   - Updated for v5.27.1
 
 5.20170531

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

@@ -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',