How do I publish the same app for multiple SDKs?

[FlyFrosty]

Hello,

I recently found out that there is an error with my clock faces.  The cure is literally adding 3 letters to my code.  However, my clock faces were auto-updated to be compatible with 5.0+ SDK watches and published.  I made the correction and found out that the approval team tests for the new SDK and not the old.  My faces fails to have the full functionality in the new watches.  How do I publish for 2 different SDK levels with one name?  The person asking for the correction is using a Sense (SDK 5.0+), so I'd hate to simply de-select Versa 3 and Sense in the App Manager since people are using it. 

[Gondwana]

Use the one GAM Project, but upload two different builds: one for SDK4 and one for SDK5+. The builds will need the same UUID, but different dependencies and targets in package.json, different filenames where necessary, etc.

[FlyFrosty]

Thanks for the response. Just to make sure I'm doing this correctly...

I export my SDK4 version with only the older model watches selected. 

Make a copy all these files and store them elsewhere. 

Use the same environment/name  (I use the Fitbit Studio) and update the code to SDK5+

Submit this file under a new version, but the same name as my previous build, back into the GAM? 

[Pietero]

I have 2 seperate package.json. I just rename them to work a different SDK. No need to duplicate files.

In gam.fitbit.com You just upload the published project. In my uploads SDK4 and SDK6 are mixed. 

[Gondwana]

Either way should be fine.