Managing hot deploys & binary deploys - best practice?


#1

We’re frequently updating our app, and using the production channel to run hot deploys.

I’m a little unsure how to fragment the deploys though, so that hot deploys only get sent to their respective binary, as opposed to a possible older binary version that will break with the new hot deploy code.

Does anybody have any best practice around this?

Cheers!