So, it’s really cool that all it takes to update production app is modify some JS files, save and run expo publish
But it also scares the hell out of me! It’s so easy for someone to accidentally forget to expo publish --release-channel staging or something and OOPS prod is updated with test code
Is there some best practice way to lock down the production channel?
It’s a very short term goal to have the publication all handled by CI/CD servers, and probably lock engineers out of the Expo account, which would protect.
But this does seem harsh, and also potentially imperfect still.
you can rollback the update for specific channel if you found pushing something wrong .
Also you can always push the update to staging first and then transfer the update in staging to production instead of directly pushing update to production.