Support multiple release channels
complete
Adam Perry
Staging, production, etc. From https://github.com/expo/expo/issues/134.
Would also need tooling to move/promote one revision from a release channel to another.
Valtýr Örn Kjartansson
It would be amazing if it were possible to specify a release channel when the app checks for an update. That would make it possible to flag users as beta testers without maintaining a separate binary with all the fuss that comes along with that. I've made a feature request for this. I'd appreciate an upvote if you'd find this feature useful.
https://expo.canny.io/feature-requests/p/release-channel-argument-in-checkforupdateasync
Brent Vatne
We launched our first version of release channels in SDK23, you can read more about it in the docs: https://docs.expo.io/versions/latest/guides/release-channels.html
We'll have some nice new features coming in SDK24 as well -- I highly recommend checking out the release channels in their current state, they work great!
Alex Russell
Brent Vatne: Interestingly I tested release channels out for the recent (standalone-but-built-by-expo) app I created and it didn't work too well to run the build command with a release channel (it kept building an old version rather than the current version).
Building from the default release channel works all the time though, so I guess for now I can use release channels to publish pre-releases and the default channel for my prod code.
But hopefully these teething trouble get fixed (or maybe they already are - this was literally on day 1-3 of the public release of channels) because, as the blog post/docs say, it'd make more sense to run a build off a specific release channel than the default one.
Brent Vatne
Alex Russell: hello! I need more information than this. In my experience it has worked as expected and this is the first I have heard of a standalone build not pointing to the correct release channel. I suspect you may have made a typo or done something wrong on your end 😅 can you post to forums.expo.io with more information?
Alex Russell
Brent Vatne: Hi sorry I wasn't really going down the support route with that comment, hence not giving much detail (though I'm pretty sure it wasn't user error, I was literally amending files, upping the version in app.json and then
up+enter
ing in my terminal in order to build a new version with the same release channel - and it still somehow used the old
version number, but as soon as I did a build with no release channel it used the new version number).Anyway, this was a couple of weeks ago now, and I imagine the release channel stuff is being tweaked behind the scenes all the time, so I'll try again soon and if it's still not working right I'll get on the forum. As you say, I could still be something on my part.
Brent Vatne
complete
Zach Reed
Can mark this complete or in progress now I think with the update of: https://blog.expo.io/expo-sdk-v23-0-0-is-now-available-be0a8c655414 - Where this is "Beta support for Release Channels"
Karel Crombecq
I was just talking about this on the Expo Slack. Would be great!
Brent Vatne
in progress
Serhii Palash
I have created related request. Please vote for it.
"Granting publication rights to another user for a particular project"
Brent Vatne
planned
Noah Lively
It would also be good to restrict cloud pushes to only be downloaded by the same minor version. I.e. A bundle published as version 1.1 can be updated by all devices that have downloaded 1.1... however if a new bundle is published to 1.2, it isn't downloaded by devices on 1.1.
This would really help manage detached apps in the wild and prevent potentially missing dependencies
Tim Brandin
Noah Lively: awesome idea! Would def help!