Feature: Channels #14

New issue

Open

opened 2026-09-07 13:40:11 +00:00 by uwayss · 0 comments

uwayss commented

2026-09-07 13:40:11 +00:00

Owner

The problem

Currently, everyone receives the same bundle. There's no way to ship an experimental build to internal testers without exposing it to everyone.

What I'm planning to do

Support multiple channels, each pointing at its own set of updates.
Developers upload a bundle to a specific channel, clients only receive updates from the channel they were built with or set to use

Clients already send expo-channel-name on the manifest request, so this is just routing based on that header and not a completely new endpoint.

TODOs

Implement channel creation/listing/deletion
Set a bundle's target channel
Swap a bundle's channel without rebuilding
Resolve a manifest request's channel header correctly.
Handle/set up a fallback channel mechanism for unknown/missing channel headers

## The problem Currently, everyone receives the same bundle. There's no way to ship an experimental build to internal testers without exposing it to everyone. ## What I'm planning to do Support multiple channels, each pointing at its own set of updates. Developers upload a bundle to a specific channel, clients only receive updates from the channel they were built with or set to use Clients already send `expo-channel-name` on the manifest request, so this is just routing based on that header and not a completely new endpoint. ## TODOs - [ ] Implement channel creation/listing/deletion - [ ] Set a bundle's target channel - [ ] Swap a bundle's channel without rebuilding - [ ] Resolve a manifest request's channel header correctly. - [ ] Handle/set up a fallback channel mechanism for unknown/missing channel headers

uwayss added the

enhancement

label

2026-09-07 13:40:50 +00:00