Skip to content
This repository was archived by the owner on Dec 29, 2025. It is now read-only.

Comments

Update dependency @cosmjs/cosmwasm-stargate to ^0.37.0#31

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/cosmjs-cosmwasm-stargate-0.x
Open

Update dependency @cosmjs/cosmwasm-stargate to ^0.37.0#31
renovate[bot] wants to merge 1 commit intomainfrom
renovate/cosmjs-cosmwasm-stargate-0.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Aug 11, 2025

This PR contains the following updates:

Package Change Age Confidence
@cosmjs/cosmwasm-stargate (source) ^0.31.0 -> ^0.37.0 age confidence

Release Notes

cosmos/cosmjs (@​cosmjs/cosmwasm-stargate)

v0.37.0

Compare Source

Added
  • @​cosmjs/tendermint-rpc: Add dedicated Comet1Client for compatibility with
    CometBFT 1.x RPC. The module comet1 contains all CometBFT 1.x specific
    types. connectComet now uses this client automatically when connecting to a
    1.x RPC backend. Before CosmJS 0.37 the Comet38Client was used for both 0.38
    and 1.0 backends. However it turned out that there are breaking API changes
    between those versions. (#​1787)
Changed
  • all: The package.jsons now all use the modern exports field instead of the
    classic main/types to define the entry points. This ensures only symbols
    from the top level module can be imported (like
    import { toBech32 } from "@​cosmjs/encoding"). Other import paths like
    import { toBech32 } from "@​cosmjs/encoding/src/bech32" are not allowed
    anymore. As all public interfaces used to be exported from the top level for a
    long time, this should not affect most users. However, if you accidentally
    imported a subpath before you will get an error now. This can typically be
    resolved like this:

    -import { toBech32 } from "@​cosmjs/encoding/src/bech32"
    +import { toBech32 } from "@​cosmjs/encoding"

    (#​1819)

  • Replace bech32 implementation by @​scure/base. This changes a bunch of error
    messages but is otherwise not breaking user code. (#​1825)

  • Replace bip39 implementation by @​scure/bip39. This changes a bunch of error
    messages but is otherwise not breaking user code. (#​1843)

  • @​cosmjs/tendermint-rpc: connectComet now returns a Comet1Client when a
    CometBFT 1.x RPC is found. CometClient now includes Comet1Client.
    (#​1827)

  • @​cosmjs/cosmwasm-stargate: use native compression APIs instead of pako for
    gzip. (#​1764)

Deprecated
  • The use of encrypted wallet storage is deprecated. In particular this means:

    • Secp256k1HdWallet.serialize/.serializeWithEncryptionKey (since 0.36.0)
    • Secp256k1HdWallet.deserialize/.deserializeWithEncryptionKey (since
      0.36.0)
    • DirectSecp256k1HdWallet.serialize/.serializeWithEncryptionKey (since
      0.36.0)
    • DirectSecp256k1HdWallet.deserialize/.deserializeWithEncryptionKey (since
      0.36.0)
    • executeKdf from @​cosmjs/amino and @​cosmjs/proto-signing (since
      0.36.0/0.37.0)

    If you are using any of those methods, please comment at
    #​1796.

  • @​cosmjs/tendermint-rpc: Deprecate the Tendermint/CometBFT 0.34 client
    (isTendermint34Client/Tendermint34Client as well as all related types).
    This will be removed in the next version of CosmJS:
    #​1866

v0.36.2

Compare Source

Fixed
  • @​cosmjs/crypto: Set min version of @​noble/hashes to 1.8.0 to avoid errors like

    Cannot find module '@​noble/hashes/legacy' from
    '../../node_modules/@​cosmjs/crypto/build/ripemd.js'

    We use @noble/hashes/legacy for ripemd which is only available in ^1.8.0.

v0.36.1

Compare Source

Fixed
  • @​cosmjs/crypto: Fix import path of @​noble/hashes to avoid bunding issue

    Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './sha2.js' is not
    defined by "exports" in …

    In @​noble/hashes version >=1.0.0 <1.8.0 the import paths must not contain the
    .js suffix. This issue was intoduced in CosmJS 0.35.0 but only affects users
    who have @​noble/hashes lower than 1.8.0 in their lockfile. (#​1817)

v0.36.0

Compare Source

Changed
Deprecated
  • The use of encrypted wallet storage is deprecated. In particular this means:

    • Secp256k1HdWallet.serialize/.serializeWithEncryptionKey
    • Secp256k1HdWallet.deserialize/.deserializeWithEncryptionKey
    • DirectSecp256k1HdWallet.serialize/.serializeWithEncryptionKey
    • DirectSecp256k1HdWallet.deserialize/.deserializeWithEncryptionKey

    If you are using any of those methods, please comment at
    #​1796.

    A scream test was established which slows down the key derivation function a
    lot. This simulates the use of a pure-JS implementation of Argon2 which we
    will use on one of the next releases. If this causes problems for your app,
    switch back to ^0.35.0 and comment in the issue.

    (#​1797)

v0.35.2

Compare Source

Fixed
  • @​cosmjs/crypto: Set min version of @​noble/hashes to 1.8.0 to avoid errors like

    Cannot find module '@​noble/hashes/legacy.js' from
    '../../node_modules/@​cosmjs/crypto/build/ripemd.js'

    We use @noble/hashes/legacy.js for ripemd which is only available in ^1.8.0.

v0.35.1

Compare Source

Deprecated
  • The use of encrypted wallet storage is deprecated. In particular this means:

    • Secp256k1HdWallet.serialize/.serializeWithEncryptionKey
    • Secp256k1HdWallet.deserialize/.deserializeWithEncryptionKey
    • DirectSecp256k1HdWallet.serialize/.serializeWithEncryptionKey
    • DirectSecp256k1HdWallet.deserialize/.deserializeWithEncryptionKey
    • executeKdf from @​cosmjs/amino and @​cosmjs/proto-signing

    If you are using any of those methods, please comment at
    #​1796.

v0.35.0

Compare Source

Added
Changed

v0.34.1

Compare Source

Deprecated
  • The use of encrypted wallet storage is deprecated. In particular this means:

    • Secp256k1HdWallet.serialize/.serializeWithEncryptionKey
    • Secp256k1HdWallet.deserialize/.deserializeWithEncryptionKey
    • DirectSecp256k1HdWallet.serialize/.serializeWithEncryptionKey
    • DirectSecp256k1HdWallet.deserialize/.deserializeWithEncryptionKey
    • executeKdf from @​cosmjs/amino and @​cosmjs/proto-signing

    If you are using any of those methods, please comment at
    #​1796.

v0.34.0

Compare Source

Fixed
Added
Changed
  • Replace axios with cross-fetch (#​1645)
  • Fix block events in CometBFT 0.38 API (begin_block_events/end_block_events
    -> finalize_block_events) in RpcBlockResultsResponse and
    BlockResultsResponse (#​1612)
  • @​cosmjs/crypto: Migrate from elliptic to noble-curves (#​1272).

v0.33.1

Compare Source

Fixed

v0.33.0

Compare Source

Changed

v0.32.4

Compare Source

Fixed
Added
Changed

v0.32.3

Compare Source

Changed
  • @​cosmjs/amino: Add IBC denom support to parseCoins and use the same
    implementation in all those imports:

    import { parseCoins } from "@&#8203;cosmjs/proto-signing";
    // equals
    import { parseCoins } from "@&#8203;cosmjs/stargate";
    // equals
    import { parseCoins } from "@&#8203;cosmjs/amino";
  • @​cosmjs/stargate: Let parseRawLog gracefully handle empty strings to better
    support Cosmos SDK 0.50 inputs. (#​1564)

Fixed

v0.32.2

Compare Source

Fixed
Changed
  • @​cosmjs/tendermint-rpc: Require protocol to be set in endpoint URLs (https://,
    http://, wss:// or ws://). Otherwise an error is raised instead of falling
    back to ws://. (#​1527)

v0.32.1

Compare Source

Fixed

v0.32.0

Compare Source

Added
Fixed
Changed
  • all: Upgrade cosmjs-types to 0.9.0. This makes a few fields non-optional. It
    changes all 64 bit int fields from type long to bigint. As part of the
    upgrade, the types do not require the long and protobufjs anymore.
    (#​1484)
  • all: gasWanted/gasUsed fields were changed from type number to bigint
    to supported cases where users put very high gas values in there (#​1465).
  • Drop support for Node.js 14 and add support for Node.js 20. (#​1421)
  • @​cosmjs/tendermint-rpc: Remove Adaptor abstractions which are not needed
    anymore by haing a dedicated client for each backend.
  • @​cosmjs/tendermint-rpc: Add
    CometClient = Tendermint34Client | Tendermint37Client | Comet38Client and
    connectComet for auto-detecting the right client for a provided endpoint.
  • @​cosmjs/stargate: Let SigningStargateClient.createWithSigner and
    StargateClient.create take a CometClient argument, adding support for
    Comet38Client. The auto-detection in
    SigningStargateClient.connectWithSigner and StargateClient.connect now
    supports CometBFT 0.38. Rename
    StargateClient.getTmClient/.forceGetTmClient to
    .getCometClient/.forceGetCometClient.
  • @​cosmjs/cosmwasm-stargate: Let SigningCosmWasmClient.createWithSigner and
    CosmWasmClient.create take a CometClient argument, adding support for
    Comet38Client. The auto-detection in
    SigningCosmWasmClient.connectWithSigner and CosmWasmClient.connect now
    supports CometBFT 0.38. Rename
    CosmWasmClient.getTmClient/.forceGetTmClient to
    .getCometClient/.forceGetCometClient.
  • @​cosmjs/stargate: Remove interfaces SearchBySentFromOrToQuery and
    SearchByHeightQuery which became obsolete with the searchTx change in
    0.31.0.
Deprecated
  • @​cosmjs/tendermint-rpc: CometClient should be used instead of
    TendermintClient.
  • @​cosmjs/stargate: Deprecate SigningStargateClient.sendIbcTokens. Please use
    signAndBroadcast + MsgTransferEncodeObject instead. (#​1493)
  • @​cosmjs/stargate: Deprecate IndexedTx.rawLog and DeliverTxResponse.rawLog
    because those fields are unset from Cosmos SDK 0.50 onwards (see
    here).

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Aug 11, 2025

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@renovate renovate bot force-pushed the renovate/cosmjs-cosmwasm-stargate-0.x branch 2 times, most recently from 98d97db to 4d535ea Compare August 13, 2025 13:11
@renovate renovate bot changed the title Update dependency @cosmjs/cosmwasm-stargate to ^0.34.0 Update dependency @cosmjs/cosmwasm-stargate to ^0.35.0 Aug 13, 2025
@renovate renovate bot force-pushed the renovate/cosmjs-cosmwasm-stargate-0.x branch from 4d535ea to 71d3916 Compare August 14, 2025 15:53
@renovate renovate bot changed the title Update dependency @cosmjs/cosmwasm-stargate to ^0.35.0 Update dependency @cosmjs/cosmwasm-stargate to ^0.36.0 Aug 14, 2025
@renovate renovate bot force-pushed the renovate/cosmjs-cosmwasm-stargate-0.x branch 4 times, most recently from 2612560 to 28546f0 Compare September 4, 2025 18:05
@renovate renovate bot force-pushed the renovate/cosmjs-cosmwasm-stargate-0.x branch from 28546f0 to 88d774d Compare October 2, 2025 16:00
@renovate renovate bot force-pushed the renovate/cosmjs-cosmwasm-stargate-0.x branch 2 times, most recently from 11b7438 to dfe6d57 Compare October 29, 2025 15:36
@renovate renovate bot changed the title Update dependency @cosmjs/cosmwasm-stargate to ^0.36.0 Update dependency @cosmjs/cosmwasm-stargate to ^0.37.0 Oct 29, 2025
@renovate renovate bot force-pushed the renovate/cosmjs-cosmwasm-stargate-0.x branch from dfe6d57 to d2e5601 Compare November 15, 2025 08:06
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants