Repository navigation
chore: release Open Sync 0.5.0 - #54
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.
Why
#53 makes the shared cron the sole source polling cadence and adds forward migrations for existing host databases. A new package version is needed so embedding applications can adopt it safely.
How
Bump Open Sync and the example integrations' peer dependency to 0.5.0. The minor version marks removal of
intervalMsandnextDueAt; existing databases migrate automatically when reopened with their original data directory.Hosts upgrading from 0.3.x must also adopt the 0.4.0 cron startup contract: await
sync.start(), handlerunOpenSyncCron()before compiled server initialization, and build withsplitting: true. Stop and back up the host before upgrading; reverting to an older binary requires restoring that backup.