Repository navigation
docs: going back to dev or main keeps history - #565
Merged
Merged
Conversation
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.
The What's New and the Developer / Sync Notes still said an in-place downgrade from next-dev to dev gets unreliable and can need a delete and reinstall. As the corrected note in #534 says, an older build migrates the newer store down and keeps glucose, carbs, insulin and dosing history; only the attributes added since Modelv4 (backfill flags, receive times) are dropped. Both docs now say that, and the dev notes mention LoopKit/LoopKit#650 and its revert, LoopKit/LoopKit#652.