chore: version packages - #849
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
August 25, 2026 13:46
28d3a02 to
b6fbe9e
Compare
Contributor
Author
✅ E2E Dev Smoke — passing
4 passed · 0 failed · 0 skipped · 32s |
Contributor
Author
E2E Examples — all passedAll examples passed in the latest run. |
Contributor
Author
E2E Playground results
Details
📥 Download full HTML report (open the run → Artifacts → |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 26, 2026 13:25
b6fbe9e to
eb1f229
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 26, 2026 13:37
eb1f229 to
72df161
Compare
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
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 publish to npm yourself or setup this action to publish 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
@lifi/wallet-management@4.2.0
Minor Changes
1d7bf36Thanks @chybisov! - Add Stellar (STL) support. Introduces the@lifi/widget-provider-stellarpackage, which integrates the Stellar Wallets Kit (Freighter, xBull, Lobstr, Rabet, Hana, Klever, OneKey, and Bitget) and exposes the connected account and signer to the widget. Adds the baseStellarContext, wires Stellar into wallet management (account aggregation, combined wallet list, and the connect menu), enables the Stellar ecosystem in the widget's wallet providers, and makes Stellar selectable as a route chain.Patch Changes
#847
874158cThanks @chybisov! - Update@lifi/sdkto^4.5.0and each@lifi/sdk-provider-*package to its latest release.#847
874158cThanks @chybisov! - Update runtime dependencies, including@lifi/sdk4.4.0 and the@lifi/sdk-provider-*packages.#852
a1cddf8Thanks @chybisov! - Update runtime dependencies, includingi18next26.4 andreact-i18next17.0.12.Updated dependencies [
1d7bf36,874158c,874158c]:@lifi/widget@4.6.0
Minor Changes
1d7bf36Thanks @chybisov! - Add Stellar (STL) support. Introduces the@lifi/widget-provider-stellarpackage, which integrates the Stellar Wallets Kit (Freighter, xBull, Lobstr, Rabet, Hana, Klever, OneKey, and Bitget) and exposes the connected account and signer to the widget. Adds the baseStellarContext, wires Stellar into wallet management (account aggregation, combined wallet list, and the connect menu), enables the Stellar ecosystem in the widget's wallet providers, and makes Stellar selectable as a route chain.Patch Changes
#827
1d7bf36Thanks @chybisov! - Stop showing the insufficient gas warning on Stellar when the route bridges enough XLM to cover the destination step, so a receiver with an empty XLM balance no longer sees a false warning.#827
1d7bf36Thanks @chybisov! - Keep the unsupported-receiver block consistent across the limit order and checkout flows, so a route that cannot honour a required receiver stays blocked everywhere.#847
874158cThanks @chybisov! - Update@lifi/sdkto^4.5.0and each@lifi/sdk-provider-*package to its latest release.#852
a1cddf8Thanks @chybisov! - Update runtime dependencies, includingi18next26.4,react-i18next17.0.12, Motion 13.1.1 and TanStack Router 1.170.32.#847
874158cThanks @chybisov! - Update runtime dependencies, including Motion 13,react-intersection-observer11,@lifi/sdk4.4.0 and MUI 9.3.Updated dependencies [
1d7bf36,874158c,874158c,a1cddf8]:@lifi/widget-provider@4.4.0
Minor Changes
1d7bf36Thanks @chybisov! - Add Stellar (STL) support. Introduces the@lifi/widget-provider-stellarpackage, which integrates the Stellar Wallets Kit (Freighter, xBull, Lobstr, Rabet, Hana, Klever, OneKey, and Bitget) and exposes the connected account and signer to the widget. Adds the baseStellarContext, wires Stellar into wallet management (account aggregation, combined wallet list, and the connect menu), enables the Stellar ecosystem in the widget's wallet providers, and makes Stellar selectable as a route chain.Patch Changes
#847
874158cThanks @chybisov! - Update@lifi/sdkto^4.5.0and each@lifi/sdk-provider-*package to its latest release.#847
874158cThanks @chybisov! - Update runtime dependencies, including@lifi/sdk4.4.0 and the@lifi/sdk-provider-*packages.@lifi/widget-provider-stellar@4.2.0
Minor Changes
1d7bf36Thanks @chybisov! - Add Stellar (STL) support. Introduces the@lifi/widget-provider-stellarpackage, which integrates the Stellar Wallets Kit (Freighter, xBull, Lobstr, Rabet, Hana, Klever, OneKey, and Bitget) and exposes the connected account and signer to the widget. Adds the baseStellarContext, wires Stellar into wallet management (account aggregation, combined wallet list, and the connect menu), enables the Stellar ecosystem in the widget's wallet providers, and makes Stellar selectable as a route chain.Patch Changes
#853
f977094Thanks @chybisov! - Keep the Stellar Wallets Kit off the server render. The kit's wallet modules readwindowin their constructors, so a framework that server-renders the provider — Next.js prerendering, for example — crashed withReferenceError: window is not definedinsideinitStellarWalletsKit. Without awindowthe store is now built inert: no kit, no availability probe, no listeners. The browser still builds the real singleton in its own module instance, and because its first render also shows no wallets and no address, hydration stays consistent.#847
874158cThanks @chybisov! - Update@lifi/sdkto^4.5.0and each@lifi/sdk-provider-*package to its latest release.Updated dependencies [
1d7bf36,874158c,874158c]:@lifi/widget-provider-bitcoin@4.2.3
Patch Changes
#827
1d7bf36Thanks @chybisov! - Update@lifi/sdkto^4.4.0and each ecosystem SDK provider to its latest release.#847
874158cThanks @chybisov! - Update@lifi/sdkto^4.5.0and each@lifi/sdk-provider-*package to its latest release.#847
874158cThanks @chybisov! - Update runtime dependencies, including@lifi/sdk4.4.0 and the@lifi/sdk-provider-*packages.Updated dependencies [
1d7bf36,874158c,874158c]:@lifi/widget-provider-ethereum@4.1.4
Patch Changes
#827
1d7bf36Thanks @chybisov! - Update@lifi/sdkto^4.4.0and each ecosystem SDK provider to its latest release.#847
874158cThanks @chybisov! - Update@lifi/sdkto^4.5.0and each@lifi/sdk-provider-*package to its latest release.#847
874158cThanks @chybisov! - Update runtime dependencies, including@lifi/sdk4.4.0 and the@lifi/sdk-provider-*packages.Updated dependencies [
1d7bf36,874158c,874158c]:@lifi/widget-provider-solana@4.1.4
Patch Changes
#827
1d7bf36Thanks @chybisov! - Update@lifi/sdkto^4.4.0and each ecosystem SDK provider to its latest release.#847
874158cThanks @chybisov! - Update@lifi/sdkto^4.5.0and each@lifi/sdk-provider-*package to its latest release.#847
874158cThanks @chybisov! - Update runtime dependencies, including@lifi/sdk4.4.0 and the@lifi/sdk-provider-*packages.Updated dependencies [
1d7bf36,874158c,874158c]:@lifi/widget-provider-sui@4.1.4
Patch Changes
#827
1d7bf36Thanks @chybisov! - Update@lifi/sdkto^4.4.0and each ecosystem SDK provider to its latest release.#847
874158cThanks @chybisov! - Update@lifi/sdkto^4.5.0and each@lifi/sdk-provider-*package to its latest release.#847
874158cThanks @chybisov! - Update runtime dependencies, including@lifi/sdk4.4.0 and the@lifi/sdk-provider-*packages.Updated dependencies [
1d7bf36,874158c,874158c]:@lifi/widget-provider-tron@4.1.4
Patch Changes
#827
1d7bf36Thanks @chybisov! - Update@lifi/sdkto^4.4.0and each ecosystem SDK provider to its latest release.#847
874158cThanks @chybisov! - Update@lifi/sdkto^4.5.0and each@lifi/sdk-provider-*package to its latest release.#847
874158cThanks @chybisov! - Update runtime dependencies, including@lifi/sdk4.4.0 and the@lifi/sdk-provider-*packages.Updated dependencies [
1d7bf36,874158c,874158c]:@lifi/widget-checkout@4.0.2
Patch Changes
#827
1d7bf36Thanks @chybisov! - Keep the unsupported-receiver block consistent across the limit order and checkout flows, so a route that cannot honour a required receiver stays blocked everywhere.#827
1d7bf36Thanks @chybisov! - Update@lifi/sdkto^4.4.0and each ecosystem SDK provider to its latest release.#847
874158cThanks @chybisov! - Update runtime dependencies, including Motion 13,@lifi/sdk4.4.0 and MUI 9.3.#847
874158cThanks @chybisov! - Update@lifi/sdkto^4.5.0and each@lifi/sdk-provider-*package to its latest release.#852
a1cddf8Thanks @chybisov! - Update runtime dependencies, includingi18next26.4,react-i18next17.0.12, Motion 13.1.1 and TanStack Router 1.170.32.Updated dependencies [
1d7bf36,1d7bf36,1d7bf36,874158c,874158c,a1cddf8,a1cddf8,874158c]:@lifi/widget-provider-mesh@4.0.2
Patch Changes
874158cThanks @chybisov! - Update runtime dependencies, including@lifi/sdk4.4.0 and the@lifi/sdk-provider-*packages.1d7bf36,874158c,874158c]:@lifi/widget-provider-transak@4.0.2
Patch Changes
1d7bf36,874158c,874158c]: