Well, that was certainly annoying. I'm trying to create a new application manifest (deployment manifest), and if I use the -MinVersion (-mv) option as specified in the Mage documentation, it fails with the error, "The minimum version specified is not valid." I'm guessing that this goes hand in hand with the bug that I ran into earlier where you can't do anything but a check after install when using mage. For that defect, I ended up running some code to replace the <expiration maximumAge="0" unit="days" /> tag with <beforeApplicationStartup/>, since mage won't do it correctly.
To get around this problem, you end up needing to run mage twice. First, to create the deployment manifest, and second to add the -MinVersion property to the app. Like so (in MSBuild):
<Exec WorkingDirectory="$(DeployTempDir)" Command="mage.exe -New Deployment -ToFile MyApp.application -Version $(BuildLabel) -Name "App" -providerUrl https://www.myurl.com/myapp/myapp.application -AppManifest $(BuildLabel)\MyApp.exe.manifest -Install true"></Exec>
<Exec WorkingDirectory="$(DeployTempDir)" Command="mage.exe -Update MyApp.application -MinVersion $(BuildLabel)"></Exec>
Kinda silly, but it works.