Prepare v12.0.0-rc.3 for release

[Shaptic]

This release will include the following PRs:

• feat!: export ContractClient et al. in contract; rename SorobanRpc to rpc #962
• add a from method to ContractClient to instantiate from a contractId #960
• An update to stellar-base (v12.0.0-rc.1)
• Add StateChanges in SimulateTransaction API response #963

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@types/node@20.12.12	None	+1	2.13 MB	types
npm/@typescript-eslint/parser@7.9.0	Transitive: filesystem	+8	1.27 MB	jameshenry
npm/chai-as-promised@7.1.2	None	0	28.3 kB	chaijs
npm/core-js-compat@3.37.1	None	0	731 kB	zloirock
npm/eslint-plugin-jsdoc@48.2.5	Transitive: unsafe	+10	774 kB
npm/picocolors@1.0.1	environment	0	5.15 kB	alexeyraspopov

🚮 Removed packages: npm/@types/node@20.12.10, npm/@typescript-eslint/parser@7.8.0, npm/chai-as-promised@7.1.1, npm/core-js-compat@3.37.0, npm/eslint-plugin-jsdoc@48.2.4

View full report↗︎

[github-actions]

Size Change: 0 B

Total Size: 12 MB

ℹ️ View Unchanged

Filename	Size
dist/stellar-sdk.js	6.68 MB
dist/stellar-sdk.min.js	5.28 MB

_{compressed-size-action}

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note
Filesystem access	npm/update-browserslist-db@1.0.16	Module: fs Location: Package overview

View full report↗︎

Next steps

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/update-browserslist-db@1.0.16

[chadoh]

Let's goooooo