Bumping version number to v0.9.13 to avoid confusing anyone with a pr…

…eviously spun v0.9.12 which was uploaded to the GitHub downloads page without any version change in the code or new git tag.

build/mt-dists/default.mk

@@ -1,5 +1,5 @@
 PRODUCT_NAME = Melody
-PRODUCT_VERSION = 0.9.11
+PRODUCT_VERSION = 0.9.13
 SCHEMA_VERSION = 4.0076
 # Corresponds to MT 4.32
 API_VERSION = 4.32

lib/MT.pm

@@ -35,13 +35,13 @@ BEGIN {
         # the Melody version for the dist name and other variables while
         # still maintaining the API version ($VERSION) for plugins to
         # test against for compatibility (i.e. "use MT 4.32;")
-        use version; our $VERSION = qv('0.9.11'); # MakeMaker stops here
+        use version; our $VERSION = qv('0.9.13'); # MakeMaker stops here
         $PRODUCT_VERSION          = $VERSION;    # The rightful resting place
         $VERSION                  = '4.32';      # The true API version
         $SCHEMA_VERSION           = '4.0076';
         $PRODUCT_NAME             = 'Melody';
         $PRODUCT_CODE             = 'OM';
-        $VERSION_ID               = '0.9.11 (MT 4.32+)';
+        $VERSION_ID               = '0.9.13 (MT 4.32+)';
         $PORTAL_URL               = 'http://openmelody.org';
     }
     else { 

php/mt.php

@@ -7,8 +7,8 @@
 
 if('__MAKE_ME__' == '__MAKE_' . 'ME__') { # If make is not run
     define('VERSION', '4.32');
-    define('VERSION_ID', '0.9.11 (MT 4.32+)');
-    define('PRODUCT_VERSION', '0.9.11');
+    define('VERSION_ID', '0.9.13 (MT 4.32+)');
+    define('PRODUCT_VERSION', '0.9.13');
     define('PRODUCT_NAME', 'Melody');    
 } else {
     define('VERSION', '__API_VERSION__');