-
Couldn't load subscription status.
- Fork 139
Release Protocol 23 #805
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
Release Protocol 23 #805
Conversation
* 1. Run the generator:
Change the commit hash to the right sha of stellar/stellar-xdr.
Add any new filenames (if needed: here Stellar-exporter.x for Galexie).
Run `make reset-xdr` from the project root.
* 2. Post-generation fixups to work around bugs or project-specific stuff:
* Move `xdr.Operation` into a hidden namespace to avoid conflicts with the
SDK's `Operation`.
* Minimize the diff by running `sed -ie s/\"/\'/g types/{curr,next}.d.ts`
(because the generator uses a different prettier config--this could
probably be fixed in the generator itself, but this is easy enough
for now).
* Add workarounds:
- `type Hash = Opaque[];` is a necessary alias that doesn't get gen'd
- `Hyper`, `UnsignedHyper`, and `ScSpecEventV0` need their signatures
fixed because it should take a proper `Array` instead of a naked `[]`
(enforced by `yarn lint`).
- Some constants aren't generated correctly, ref. the linked issue
* 3. Accommodate XDR additions or renames:
* This accounts for any fields that encountered a rename as part
of the new XDR version. In this case, `readBytes` was renamed to
`diskReadBytes` because it's measured differently as a result of
Core's state living in memory rather than on disk in most cases.
* It also accounts for the unused extension point actually having
a name now, so `xdr.ExtensionPoint` needs to use the structure-
specific `xdr.SorobanTransactionDataExt`, instead.
* Add docs to README for completeness
* Migrate to @noble/curves instead of sodium+nacl
|
Size Change: +147 kB (+4.46%) Total Size: 3.44 MB
|
* Prevent CBs and LPs from being used as arguments
* Remove secret keys from docs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approved, I see other pr's still need to merge to protocol-23, but this is just release process flow, and you know when to merge.
* Upgrade packages, add changelog, bump version * Bump node version, drop sodium-native refs * Update jobs to latest and Node 20 * Update tag used for publishing
No description provided.