Version Packages - #610
Closed
github-actions[bot] wants to merge 1 commit into
Closed
Version Packages#610github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
requested review from
a team,
ComradeAERGO and
Justkant
as code owners
September 21, 2026 10:20
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 29, 2026 14:46
fbadd26 to
05d997d
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@ledgerhq/wallet-api-client@1.16.0
Minor Changes
635d378Thanks @CremaFR! - Addaccount.getMaxSpendable({ accountId }) -> { maxSpendable }. The wallet returns the single-transaction send-max heuristic for one account (atomic amount as a string). Hosts that do not implement the method reject with "not implemented".Patch Changes
#609
e7278ddThanks @gre-ledger! - chore(deps): bump @ledgerhq/hw-transport to 6.36.0 and drop its patch@ledgerhq/hw-transportmoved out of theledger-livemonorepo into the newLedgerHQ/ts-libsmonorepo and was republished from there as6.36.0with noAPI change. It pulls
@ledgerhq/devices8.18.0and@ledgerhq/logs6.19.0.The
@ledgerhq/hw-transport@6.35.3patch is removed: it existed only to retypeTransport._eventsfromEventEmitter<[never]>to a plainEventEmittersotscdeclaration emit would pass under@types/node25.6.36.0shipsEventEmitter<any>, which satisfies theEventMapconstraint on its own.Updated dependencies [
635d378]:@ledgerhq/wallet-api-core@2.1.0
Minor Changes
635d378Thanks @CremaFR! - Addaccount.getMaxSpendable({ accountId }) -> { maxSpendable }. The wallet returns the single-transaction send-max heuristic for one account (atomic amount as a string). Hosts that do not implement the method reject with "not implemented".@ledgerhq/wallet-api-server@3.5.0
Minor Changes
635d378Thanks @CremaFR! - Addaccount.getMaxSpendable({ accountId }) -> { maxSpendable }. The wallet returns the single-transaction send-max heuristic for one account (atomic amount as a string). Hosts that do not implement the method reject with "not implemented".Patch Changes
635d378]:@ledgerhq/wallet-api-simulator@2.4.0
Minor Changes
635d378Thanks @CremaFR! - Addaccount.getMaxSpendable({ accountId }) -> { maxSpendable }. The wallet returns the single-transaction send-max heuristic for one account (atomic amount as a string). Hosts that do not implement the method reject with "not implemented".Patch Changes
#609
e7278ddThanks @gre-ledger! - chore(deps): bump @ledgerhq/hw-transport to 6.36.0 and drop its patch@ledgerhq/hw-transportmoved out of theledger-livemonorepo into the newLedgerHQ/ts-libsmonorepo and was republished from there as6.36.0with noAPI change. It pulls
@ledgerhq/devices8.18.0and@ledgerhq/logs6.19.0.The
@ledgerhq/hw-transport@6.35.3patch is removed: it existed only to retypeTransport._eventsfromEventEmitter<[never]>to a plainEventEmittersotscdeclaration emit would pass under@types/node25.6.36.0shipsEventEmitter<any>, which satisfies theEventMapconstraint on its own.Updated dependencies [
635d378,e7278dd]:@ledgerhq/wallet-api-client-react@1.4.35
Patch Changes
635d378,e7278dd]:@ledgerhq/wallet-api-manifest-validator@0.8.7
Patch Changes
635d378]:@ledgerhq/wallet-api-manifest-validator-cli@0.1.72
Patch Changes
635d378]:@ledgerhq/wallet-api-tools@0.7.12
Patch Changes
635d378,e7278dd]:@ledgerhq/client-nextjs@0.1.57
Patch Changes
635d378,e7278dd]: