chore(release): new version #76
Open
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@openwallet-foundation/[email protected]
Minor Changes
f626ebc: chore: drop support for Node 18
f0ae878: feat: update to Askar 0.5.0 release.
f626ebc: rewrite the Node.JS FFI integration based on Koffi. This enabled Node.JS 24 support and provides a more modern integration
Patch Changes
f626ebc: feat: support Node.JS 24
a4f1969: docs: update version compatibility in readme
9121e2a: fix: wrap the askar registration with a
NativeAskarclass that exposes two static members: a.instancegetter andregistermethod.Previously when you did not import the native askar library on the first line (or above all logic that uses Askar) the reference to Askar would be undefined. (i.e. askar-shared is imported before askar-react-native or askar-nodejs)
The
registerAskarmethod andaskarproperty are kept for backwards compatibility, but these are still prone to the same error.registerAskarintegrated with the newNativeAskarclass, and so all usages within the shared library, as well as the nodejs and react-native wrappers will be fixed. We recommend to update to the newNativeAskarclass for all other usages.Updated dependencies [f626ebc]
Updated dependencies [f0ae878]
Updated dependencies [9121e2a]
@openwallet-foundation/[email protected]
Minor Changes
f626ebc: chore: drop support for Node 18
f0ae878: feat: update to Askar 0.5.0 release.
Patch Changes
a4f1969: docs: update version compatibility in readme
9121e2a: fix: wrap the askar registration with a
NativeAskarclass that exposes two static members: a.instancegetter andregistermethod.Previously when you did not import the native askar library on the first line (or above all logic that uses Askar) the reference to Askar would be undefined. (i.e. askar-shared is imported before askar-react-native or askar-nodejs)
The
registerAskarmethod andaskarproperty are kept for backwards compatibility, but these are still prone to the same error.registerAskarintegrated with the newNativeAskarclass, and so all usages within the shared library, as well as the nodejs and react-native wrappers will be fixed. We recommend to update to the newNativeAskarclass for all other usages.Updated dependencies [f626ebc]
Updated dependencies [f0ae878]
Updated dependencies [9121e2a]
@openwallet-foundation/[email protected]
Minor Changes
f626ebc: chore: drop support for Node 18
f0ae878: feat: update to Askar 0.5.0 release.
Patch Changes
9121e2a: fix: wrap the askar registration with a
NativeAskarclass that exposes two static members: a.instancegetter andregistermethod.Previously when you did not import the native askar library on the first line (or above all logic that uses Askar) the reference to Askar would be undefined. (i.e. askar-shared is imported before askar-react-native or askar-nodejs)
The
registerAskarmethod andaskarproperty are kept for backwards compatibility, but these are still prone to the same error.registerAskarintegrated with the newNativeAskarclass, and so all usages within the shared library, as well as the nodejs and react-native wrappers will be fixed. We recommend to update to the newNativeAskarclass for all other usages.