feat: upgrading to rxdb 15.X #100
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
BREAKING CHANGE: Upgrading to RXDB 15.X, migrations from older version has not been tested. Potentially old databases created in 14.X need to be recreated, but may not!!
Signed-off-by: Francisco Javier Ribó Labrador <elribonazo@gmail.com>
Signed-off-by: Francisco Javier Ribó Labrador <elribonazo@gmail.com>
Signed-off-by: Francisco Javier Ribó Labrador <elribonazo@gmail.com>
Signed-off-by: Francisco Javier Ribó Labrador <elribonazo@gmail.com>
elribonazo
added a commit
that referenced
this pull request
Jun 15, 2024
…s://github.com/atala-community-projects/pluto-encrypted/compare/@pluto-encrypted/leveldb@1.12.2...@pluto-encrypted/leveldb@2.0.0) (2024-06-15) ### Features * upgrading to rxdb 15.X ([#100](#100)) ([dc0c731](dc0c731)) ### BREAKING CHANGES * Upgrading to RXDB 15.X, migrations from older version has not been tested. Potentially old databases created in 14.X need to be recreated, but may not!! [skip ci]
elribonazo
added a commit
that referenced
this pull request
Jun 15, 2024
…unity-projects/pluto-encrypted/compare/@pluto-encrypted/indexdb@1.12.2...@pluto-encrypted/indexdb@2.0.0) (2024-06-15) ### Bug Fixes * database and schemas fix for last key index for prism did keys. ([b88fa6e](b88fa6e)) * eslint fix ([af68a78](af68a78)) * eslint ignore examples ([beb7e92](beb7e92)) * force inmemory release after ci issue ([5487cbd](5487cbd)) * migration fixes for testing scenarios. ([a4d8dff](a4d8dff)) * release db ([1e43c7c](1e43c7c)) * workaround to fix last keypath issue in SDKs. ([f4d1f94](f4d1f94)) * workaround to not store dids twice ([aa3b069](aa3b069)) ### Features * upgrading to rxdb 15.X ([#100](#100)) ([dc0c731](dc0c731)) ### BREAKING CHANGES * Upgrading to RXDB 15.X, migrations from older version has not been tested. Potentially old databases created in 14.X need to be recreated, but may not!! [skip ci]
|
🎉 This PR is included in version 2.0.0 🎉 The release is available on Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.0.0 🎉 The release is available on Your semantic-release bot 📦🚀 |
elribonazo
added a commit
that referenced
this pull request
Jun 15, 2024
…unity-projects/pluto-encrypted/compare/@pluto-encrypted/inmemory@1.12.3...@pluto-encrypted/inmemory@2.0.0) (2024-06-15) ### Bug Fixes * eslint fix ([af68a78](af68a78)) * eslint ignore examples ([beb7e92](beb7e92)) ### Features * upgrading to rxdb 15.X ([#100](#100)) ([dc0c731](dc0c731)) ### BREAKING CHANGES * Upgrading to RXDB 15.X, migrations from older version has not been tested. Potentially old databases created in 14.X need to be recreated, but may not!! [skip ci]
|
🎉 This PR is included in version 2.0.0 🎉 The release is available on Your semantic-release bot 📦🚀 |
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 package 14.X is reporting a medium severity vulnerability which is not really acceptable for pluto-encrypted.
All the storages, tests and functionality has been upgraded to support RXDB 15.X, but migrating an existing DB to 14.X has not been tested, for this reason the semantic release commit, will include the breaking change.
All the packages will bump a major version