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