While creating a contract, APIMAN 1.2.6 always chooses most latest API version though I select older version of API.

Steps to reproduce

I have two version of same API. Version 1 of API is the base version and version 2 of API has some additional changes to it (like some extra policy and what not). When I try to create a contract for my clientApp, I get to select what version of API I need to use as shown below

So if I select API version 1.0 and click on OK, contract is always created with latest version of API no matter what other older version of API you have.

Is this intentionally designed? If yes, the first step to choose a particular API version while creating a contract is somewhat misleading to me. In other words, when I have API having multiple versions (FaceBook API1.0,FaceBook API2.0, FaceBook API3.0) and and If I need to associate my clientapp to FaceBook API1.0, I can never create contract with my clientapp with FaceBook API1.0 since APIMAN always default the contract to most recent one (FaceBook API3.0)