[EAS] expo publish vs eas update

If you use expo:publish, it’s by default pushing to the “default” release channel with that SDK installed. So if you are still using the old expo:publish, and you add a new library, you’ll have to change the release-channel right? Or else it could try to install on older EAS builds with different dependencies but with the same SDK. Is that right?

My understanding is that the runtimeVersion key in app.json is only for expo-updates: Runtime Versions - Expo Documentation

Also, what if you change let’s the same version in the app.json or other app.json parameters. Even though you aren’t changing any native libraries, does that also require that you publish to a different releaseChannel?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.