feat(update): toggle experimental vs production update channel#341
Merged
Conversation
Devices were stuck on the baked production channel marker, so experimental OTA builds never showed up. Persist a channel preference, write a durable /data override the shell helpers also honor, and re-check after switching.
Experimental images were shipping with the static "production" marker, so Settings showed the wrong channel and checked an empty tree. Pass LOOPY_UPDATE_CHANNEL from CI into the bundle recipe.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/data/loopy/update-channel(survives A/B OS updates).loopy-update-ctl/loopy-ota-checkprefer that override over/etc/loopy/update-channel.Closes #340.
Test plan
Note
The image currently on the Pi still follows baked
production. Until this PR is in a published bundle, use a one-time manual experimental install (or wait for the in-flight appliance-release, then SSH/rauc installonce). After that, the toggle works for future updates.