George

@sreuland nice - I bumped the thread to get that merged, thanks!

Unfortunately, HTTP/2 isn't an option without a much bigger investment into finding a compatible HTTP client library for the JavaScript SDK. The current solution, [axios](https://github.com/axios/axios), doesn't support HTTP/2 (see [stellar/js-stellar-sdk#612](https://github.com/stellar/js-stellar-sdk/issues/612#issuecomment-768625890))....

Ah, so this is a breaking change, then... :facepalm: did TypeScript break this across a minor version boundary, then??

But then doing something like `number | 1` means downstream needs to handle the union :thinking: maybe I'll just include this in the next major version release? though that may...

Hey @CITGuru just want to call out this note from the latest release (#918): > There will come a future major release in which we drop support for TypeScript 5...

@chadoh lmk if you'd rather I merge this and you resolve feedback in a later PR! doesn't matter to me

Can you confirm/deny that this issue is present in the latest version?

It's a huge breaking change so I don't want to merge it just yet :sweat_smile: would rather have it alongside other big stuff

> Yarn 1 is very outdated If it ain't broke... upgrading to 3 [seems like](https://yarnpkg.com/getting-started/install) a pain in the ass for [little benefit](https://yarnpkg.com/migration/overview). But I've added the version lock as...

There is an additional schema change: the getLedgerEntries RPC response will use liveUntilLedgerSeq rather than expirationLedgerSeq in the final build (ref: stellar/soroban-tools#1029)