Add a safe TaskNotes contract upgrade workflow - #80
Merged
Conversation
# Conflicts: # src/styles.css
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.
What changed
NotFoundErrorwording; production storage remains Android, iOS, or mdbase only.Why
An updated app could previously open an older collection and then fail because its contract resources were never upgraded. The application had no safe way to explain or resolve that mismatch. Contract evolution is now a deliberate local-first interruption point rather than a later operational error.
Impact
Users get a concise source-of-truth review before changes. Safe upgrades are transactional; local divergence is preserved as a conflict. This prerelease app intentionally targets the breaking beta.25 SDK and updated TaskNotes model.
Depends on:
Validation