Repository navigation
docs: firmware notes mention ota branch (observer-firmware-dev, merge with next release) - #65
Merged
agessaman merged 2 commits intoOct 21, 2026
Conversation
Bump the header to 1.18.0 and drop the 'beta to production from v1.18' caveat now that both channels are on 1.18; ota branch only saves the choice, so name ota update too.
agessaman
marked this pull request as ready for review
October 21, 2026 03:25
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.
Updates the "Over-the-air updates" line in
firmware-notes.htmlto mentionota branch(#62/#63).Hold this until the next real release on this channel.
firmware-notes.htmlis not in the build workflow's paths-ignore, so merging this alone rebuilds and publishes the channel (new build number, fleet-wide "update available"). The live GitHub release notes were already edited by hand to match, and the next publish copies this file over them, so it must land with or before that publish.The same one-line change is open against the other channel with an identical blob, so the later dev→prod merge stays clean.