support rollback from pekko migration #590
Merged
Conversation
This file contains 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
|
@scullxbones can we merge this? |
|
I still haven't had the chance to rebuild my dev environment for this repo. I may just go the route of adapting the github action from the pekko project. I'm going to hold it until then. |
|
Merging to side branch for now. |
|
Released with |
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.
See scullxbones/pekko-persistence-mongo#14 for the equivalent compatibility change in the pekko version of the plugin and this issue scullxbones/pekko-persistence-mongo#10 for why this is necessary. Since not supporting this would result in a corrupted data store if trying to roll back, providing this capability is necessary for people to be willing to migrate safely.