Hi, I'm currently trying to modify existing apps and the underlying modules. I can see how to create and publish versions of the apps and underlying modules using the release manager to stop changes automatically going live.
However, it would be useful to be able to link to a current working version of a module or a draft release of a module when developing an app. Is it possible to do this or does the underlying module need to be published before you can develop an app with it?
We have an existing feature request to allow parent apps to show different module versions! I'll keep you updated accordingly. Thank you for adding to the context here 
@victoria Any news on this? thx!
Hey @perelin! Thanks for reaching out.
One of our focuses this year is to improve the reusability of code and UI elements. As such, we're currently in the process of scoping out a big overhaul of modules and will be sure to keep this particular feature in mind!
@Darren thanks for the update.
So how is it suppose to work currently?
I am working on a module and would like to test the changes in the apps that are integrating the module. Also because there sometimes need to be changes to those app (input/outputs, etc). How can I test changes on modules without releasing them to all users?
thanks!
Release management for modules is pretty limited in its current form, due to the fact that apps always use the most current version. The best workaround that I'm aware of is to duplicate the module before publishing a new version, so that you can do all your testing with that temporary module. 