Skip to content

Commit

Permalink
Release v12.0.0-rc.2 (#959)
Browse files Browse the repository at this point in the history
* Pin stellar-base to an exact version instead of relying on semver
* Use backend-agnostic typing for CallBuilder's timeout
  • Loading branch information
Shaptic authored May 7, 2024
1 parent b4387de commit e4db91c
Show file tree
Hide file tree
Showing 5 changed files with 130 additions and 130 deletions.
5 changes: 1 addition & 4 deletions .github/workflows/npm_publish.yml
Original file line number Diff line number Diff line change
Expand Up @@ -21,10 +21,7 @@ jobs:
run: yarn install

- name: Build, Test, and Package
run: |
npm unpublish @stellar/[email protected]
npm unpublish [email protected]
yarn preversion
run: yarn preversion
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

Expand Down
11 changes: 9 additions & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,15 +6,22 @@ A breaking change will get clearly marked in this log.

## Unreleased


## [v12.0.0-rc.2](https://github.com/stellar/js-stellar-sdk/compare/v11.3.0...v12.0.0-rc.2)

**This update supports Protocol 21**. It is an additive change to the protocol so there are no true backwards incompatibilities, but your software may break if you encounter new unexpected fields from this Protocol ([#949](https://github.com/stellar/js-stellar-sdk/pull/949)).

### Breaking Changes
* **Default timeout for transaction calls is now set to 300 seconds (5 minutes) from previous default of 10 seconds**. 10 seconds is often not enough time to review transactions before signing, especially in Freighter or using a hardware wallet like a Ledger, which would cause a `txTooLate` error response from the server. Five minutes is also the value used by the CLI, so this brings the two into alignment.
* The **default timeout for transaction calls is now set to 300 seconds (5 minutes)** from the previous default of 10 seconds. 10 seconds is often not enough time to review transactions before signing, especially in Freighter or using a hardware wallet like a Ledger, which would cause a `txTooLate` error response from the server. Five minutes is also the value used by the CLI, so this brings the two into alignment ([#956](https://github.com/stellar/js-stellar-sdk/pull/956)).

### Fixed
* Dependencies have been properly updated to pull in Protocol 21 XDR ([#959](https://github.com/stellar/js-stellar-sdk/pull/959)).


## [v12.0.0-rc.1](https://github.com/stellar/js-stellar-sdk/compare/v11.3.0...v12.0.0-rc.1)

### Breaking Changes
* **This update supports Protocol 21**. It is an additive change to the protocol so there are no true backwards incompatibilities, but your software may break if you encounter new unexpected fields from this Protocol ([#949](https://github.com/stellar/js-stellar-sdk/pull/949)).
* **Default timeout for transaction calls is now set to 60 seconds from previous default of 10**. 10 seconds is often not enough time to review transactions before signing, which would cause a `txTooLate` error response from the server.

### Fixed
* Each item in the `GetEventsResponse.events` list will now have a `txHash` item corresponding to the transaction hash that triggered a particular event ([#939](https://github.com/stellar/js-stellar-sdk/pull/939)).
Expand Down
4 changes: 2 additions & 2 deletions package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@stellar/stellar-sdk",
"version": "12.0.0-rc.1",
"version": "12.0.0-rc.2",
"description": "A library for working with the Stellar network, including communication with the Horizon and Soroban RPC servers.",
"keywords": [
"stellar"
Expand Down Expand Up @@ -145,7 +145,7 @@
"webpack-cli": "^5.0.1"
},
"dependencies": {
"@stellar/stellar-base": "^11.0.1",
"@stellar/stellar-base": "11.1.0",
"axios": "^1.6.8",
"bignumber.js": "^9.1.2",
"eventsource": "^2.0.2",
Expand Down
2 changes: 1 addition & 1 deletion src/horizon/call_builder.ts
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,7 @@ export class CallBuilder<
// in the last 15 seconds. The timeout is reset when a new message arrive.
// It prevents closing EventSource object in case of 504 errors as `readyState`
// property is not reliable.
let timeout: NodeJS.Timeout;
let timeout: ReturnType<typeof setTimeout>;

const createTimeout = () => {
timeout = setTimeout(() => {
Expand Down
Loading

0 comments on commit e4db91c

Please sign in to comment.