Release v0.11.1 (#133)

CHANGELOG.md

@@ -8,6 +8,12 @@ A breaking change should be clearly marked in this log.
 ## Unreleased
 
 
+## v0.11.1
+
+### Fixed
+* This adds sensible defaults `Server.simulateTransaction`'s response when the RPC server omits certain fields in an unexpected way ([#131](https://github.com/stellar/js-soroban-client/pull/131)).
+
+
 ## v0.11.0
 
 ### Fixed

CONTRIBUTING.md

@@ -8,16 +8,18 @@ Then please [sign the Contributor License Agreement](https://docs.google.com/for
 # Releasing
 Just like with the [js-stellar-base](https://github.com/stellar/js-stellar-base) library, there are a few important things to remember when releasing a new version of the library.
 
-In fact, you should follow [the steps there](https://github.com/stellar/js-stellar-base/blob/master/CONTRIBUTING.md#Releasing), first, except for this repository. Then, **if base has been updated**, you want to follow the additional steps here:
-
- - [ ] First, bump its version accordingly. This is straightforward: change the version field of `"stellar-base"` under the `"dependencies"` section in the SDK's [package.json](https://github.com/stellar/js-stellar-sdk/blob/master/package.json#L140), e.g.:
+In fact, you should follow [the steps there](https://github.com/stellar/js-stellar-base/blob/master/CONTRIBUTING.md#Releasing), first, except for this repository. Then:
+  - [ ] Upgrade all of the dependencies that you can, so that we don't fall too far behind. You can do this by running `yarn upgrade-interactive --latest`. You can avoid breaking changes if there is a migration necessary, but remember to handle these quickly in a subsequent release.
 
+Finally, **if base has been updated**, you want to follow the additional steps here:
+  - [ ] First, bump its version accordingly. This is straightforward: change the version field of `"stellar-base"` under the `"dependencies"` section in the SDK's [package.json](https://github.com/stellar/js-stellar-sdk/blob/master/package.json#L140), e.g.:
 ```diff
   "dependencies": {
      ...
 -    "stellar-base": "^1.0.0",
 +    "stellar-base": "^2.0.0",
   }
 ```
+  - [ ] Then, run `yarn` so that the dependency is pulled (ensuring its a valid version) and the lockfile is updated with the latest integrity details.
 
-  - [ ] Finally, run `yarn` so that the dependency is pulled (ensuring its a valid version) and the lockfile is updated with the latest integrity details. You can now commit the change and PR accordingly.
+You can now commit the change and PR accordingly.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "soroban-client",
-  "version": "0.11.0",
+  "version": "0.11.1",
   "description": "A library for working with Stellar's Soroban RPC servers.",
   "author": "Stellar Development Foundation <[email protected]>",
   "homepage": "https://github.com/stellar/js-soroban-client",
@@ -78,25 +78,25 @@
   },
   "devDependencies": {
     "@babel/cli": "^7.22.10",
-    "@babel/core": "^7.22.10",
-    "@babel/eslint-parser": "^7.22.10",
+    "@babel/core": "^7.22.11",
+    "@babel/eslint-parser": "^7.22.11",
     "@babel/eslint-plugin": "^7.22.10",
     "@babel/preset-env": "^7.22.10",
-    "@babel/preset-typescript": "^7.22.5",
+    "@babel/preset-typescript": "^7.22.11",
     "@babel/register": "^7.22.5",
-    "@definitelytyped/dtslint": "^0.0.166",
+    "@definitelytyped/dtslint": "^0.0.168",
     "@istanbuljs/nyc-config-babel": "3.0.0",
     "@stellar/tsconfig": "^1.0.2",
     "@types/chai": "^4.3.5",
     "@types/mocha": "^10.0.1",
-    "@types/node": "^20.5.1",
+    "@types/node": "^20.5.4",
     "@types/sinon": "^10.0.16",
     "@types/urijs": "^1.19.6",
     "@typescript-eslint/parser": "^6.4.1",
     "axios-mock-adapter": "^1.21.5",
     "babel-loader": "^9.1.2",
     "babel-plugin-istanbul": "^6.1.1",
-    "chai": "^4.3.7",
+    "chai": "^4.3.8",
     "chai-as-promised": "^7.1.1",
     "chai-http": "^4.4.0",
     "cross-env": "^7.0.3",