-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[js] Update to latest schema for 3P packages #242
Conversation
GitOrigin-RevId: 74d531dd26dbb7a23a7bd8a7ec75c98383dd8709
The following public packages have changed files:
There are 4 existing changesets for this branch. If additional changes have been made that require different versions for any package simply add another changeset. Any packages that depend on the planned releases will be updated and released automatically in a separate PR. Each changeset corresponds to an update in the CHANGELOG for the packages listed in the changeset. Therefore, you should add a changeset for each noteable package change that this PR contains. For example, if a PR adds two features - one feature for packages A and B and one feature for package C - you should add two changesets. One changeset for packages A and B and one changeset for package C, with a description of each feature. The feature description will end up being the CHANGELOG entry for the packages in the changeset. The following releases are planned based on the existing changesets:
Last updated by commit 0e43501 |
GitOrigin-RevId: 8b6cd6e3fab07c7d0d29d5783fa849e6a3d8bf0a
… typenames (#6182) - updates js_writer to handle nullable lists - fixes node names due to OSK/remote changes GitOrigin-RevId: ba076fb3153c2056439c9fed35f170be3bf8f2cd
fyi @coreymartin GitOrigin-RevId: e1997b4c2e3185dc05d304aff9a8eceed5f4b6a1
- adds enum for signing key types - adds property to `NodeKeyCache` to save signing key type - changes `Requester` to add signing data specific to signing key type - adds wasm packed `lightspark_crypto` lib - related PR: lightsparkdev/lightspark-crypto-uniffi#31 - adds `loadNodeSigningKey` function to client which handles both rsa and secp key types for OSK and remote signing - updates documentation to reflect new `loadNodeSigningKey` function - adds `SigningKeyLoader` classes to handle loading logic Tested using lightspark-cli lightsparkdev/webdev#6203 GitOrigin-RevId: 07daa2cd7c01610a65f5a809d37c6e69130d5330
- adds option to select node for operations that use a node - updates wasm packed lightspark_crypto lib - uses loadNodeSigningKey to unlock/provide credentials for both OSK and remote signing nodes Depends on: lightsparkdev/webdev#6089 GitOrigin-RevId: 3881892bcb99c19779fcacac3dadd97959ab75ba
GitOrigin-RevId: 7ca02542f56c2b15f688e82d6c1bb621d976c0c9
https://lightsparkgroup.slack.com/archives/C03HYQQ2HT6/p1695228450140589 Ran into issues using createHash in core because it's used in browser environments as well. Only import "crypto" if in node, and otherwise use subtle crypto. --------- Co-authored-by: Corey Martin <[email protected]> GitOrigin-RevId: 411e19138fc476550a4207759591a34eedf97f5f
If this change should result in new package versions please add a changeset before merging. You can do so by clicking the link provided by changeset bot below.