Problem with deploying to maven

This should have been answered by this Question (#3313)

I run a Maven Feed on a local proget installation (Version 5.1.19 (Build 7)) and try to deploy a package with maven version 3.5.2.
After the compilation of the package the upload starts and fails with this message.

Uploaded to releases: http://local-installation/maven2/maven-releases/test/package/artifact/0.0.1/artifact-0.0.1.jar (18 MB at 4.2 MB/s)
Uploading to releases: http://local-installation/maven2/maven-releases/test/package/artifact/0.0.1/artifact-0.0.1.pom
Progress (1): artifact-0.0.1.pom (1.7 kB)
Uploaded to releases: http://local-installation/maven2/maven-releases/test/package/artifact/0.0.1/artifact-0.0.1.pom (1.7 kB at 6.5 kB/s)
Downloading from releases: http://local-installation/maven2/maven-releases/test/package/artifact/maven-metadata.xml
[WARNING] Could not transfer metadata test.package:artifact/maven-metadata.xml from/to releases (http://local-installation/maven2/maven-releases/): Failed to transfer file: http://local-installation/maven2/maven-releases/test/package/artifact/maven-metadata.xml. Return code is: 500 , ReasonPhrase:Internal Server Error.

The feed then contains the jar and pom file and the Event Log contains two Package Created Events.
The Diagnostic Center shows the following error:

Category:
Web

Message:
An error occurred processing a GET request to http://local-/maven2/maven-releases/test/package/artifact/maven-metadata.xml: Value cannot be null. Parameter name: version

Details: 
System.ArgumentNullException: Value cannot be null.
Parameter name: version
at Inedo.ProGet.Feeds.Maven.MavenVersion.Parse (System.String version) [0x00008] in <1349015ffbf342a689ae698d25b4ab7e>:0 
at Inedo.ProGet.WebApplication.FeedEndpoints.Maven.MavenFeedHandler.ProcessRequestAsync (System.Web.HttpContext context, Inedo.ProGet.Feeds.Maven.MavenFeed feed, System.String relativeUrl) [0x00190] in <dab0761184df4cae8729746ef4194b56>:0 
at Inedo.ProGet.WebApplication.FeedEndpoints.FeedEndpointHandler+FeedRequestHandler.ProcessRequestAsync (System.Web.HttpContext context) [0x000a4] in <dab0761184df4cae8729746ef4194b56>:0

Is this really fixed?

Product: ProGet
Version: 5.1.19

thoven

Unfortunately this was a regression present in 5.1.19, but has since been fixed in 5.1.20 which was released earlier today.