Upgrade @creit.tech/stellar-wallets-kit to v2.0.1 by Copilot · Pull Request #1958 · stellar/laboratory

Copilot · 2026-03-18T19:43:12Z

Upgrades Stellar Wallets Kit from v1.9.3 to v2.0.1. This release resolves the React hydration error caused by the library injecting inline styles that conflicted with Next.js SSR.

Breaking API Changes Addressed

Static class model — StellarWalletsKit is no longer instantiated; all methods are now static:

// Before
const kit = new StellarWalletsKit({ network, modules, ... });
kit.openModal({ onWalletSelected: async (option) => { ... } });

// After
StellarWalletsKit.init({ network, modules, ... });
const { address } = await StellarWalletsKit.authModal();

Module imports — wallet modules moved from the main package to individual sub-paths:

// Before
import { AlbedoModule, FreighterModule } from "@creit.tech/stellar-wallets-kit";

// After
import { AlbedoModule } from "@creit.tech/stellar-wallets-kit/modules/albedo";
import { FreighterModule } from "@creit.tech/stellar-wallets-kit/modules/freighter";

Other changes:

WalletNetwork enum renamed to Networks
openModal({ onWalletSelected }) callback pattern replaced by authModal() returning Promise<{ address }>
buttonTheme/modalTheme replaced by a single theme property using SwkAppDarkTheme/SwkAppLightTheme
LedgerModule import path: .../modules/ledger.module → .../modules/ledger

Files Updated

WalletKitContextProvider — calls StellarWalletsKit.init() in useEffect; context now provides isInitialized: boolean instead of a class instance
ConnectWallet — static method calls; wallet ID sourced from StellarWalletsKit.selectedModule.productId post-auth
useSignWithExtensionWallet — openModal callback replaced with authModal() promise chain
InvokeContractForm — signTransaction via static call
getWalletKitNetwork — WalletNetwork → Networks

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

stellarwalletskit.dev
- Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

This section details on the original issue you should resolve

<issue_title>Upgrade Stellar Wallet Kits to the latest version</issue_title>
<issue_description>https://stellarwalletskit.dev/</issue_description>

<agent_instructions>https://github.com/Creit-Tech/Stellar-Wallets-Kit/releases/tag/v2.0.1 was released. Please update to this release</agent_instructions>

Comments on the Issue (you are @copilot in this section)
@jeesunikim this is still in beta version, but enrique confirmed that it's stable @jeesunikim I created an issue on their library end https://github.com/Creit-Tech/Stellar-Wallets-Kit/issues/79. React hydration error occurs because the library is adding an inline style which causes an error with nextjs' SSR.
I think we should update this when they release a stable version v2.</comment_new>

Fixes Upgrade Stellar Wallet Kits to the latest version #1692

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

stellar-jenkins · 2026-03-18T19:47:15Z

Preview is available here:
http://laboratory-pr1958.previews.kube001.services.stellar-ops.com/

Co-authored-by: sagpatil <1414227+sagpatil@users.noreply.github.com>

stellar-jenkins · 2026-03-18T19:59:45Z

Preview is available here:
http://laboratory-pr1958.previews.kube001.services.stellar-ops.com/

sagpatil · 2026-03-18T21:29:36Z

@copilot fix the issue with frozen lock file in the test https://github.com/stellar/laboratory/actions/runs/23264179398/job/67653173536?pr=1958

corepack enable
pnpm install
(This will rewrite pnpm-lock.yaml so the specifier matches ^2.0.1.)

Commit the updated lockfile:

bash
git add pnpm-lock.yaml
git commit -m "chore: sync pnpm-lock.yaml"
git push

Co-authored-by: sagpatil <1414227+sagpatil@users.noreply.github.com>

socket-security · 2026-03-18T21:33:36Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next@15.5.14 ⏵ 15.5.15		⁺¹⁶
	@creit.tech/stellar-wallets-kit@1.9.5 ⏵ 2.1.0	⁺²		^-1	⁺⁷

View full report

socket-security · 2026-03-18T21:33:38Z

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		License policy violation: npm `@lobstrco/signer-extension-api` under GPL-3.0 License: GPL-3.0 - The applicable license policy does not permit this license (5) (npm metadata) License: GPL-3.0 - The applicable license policy does not permit this license (5) (package/package.json) From: pnpm-lock.yaml → `npm/@creit.tech/stellar-wallets-kit@2.1.0` → `npm/@lobstrco/signer-extension-api@2.0.0` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: 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@socket.dev`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@lobstrco/signer-extension-api@2.0.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm `@trezor/blockchain-link` under LicenseRef-T-RSL License: LicenseRef-T-RSL - The applicable license policy does not permit this license (5) (package/LICENSE.md) From: pnpm-lock.yaml → `npm/@creit.tech/stellar-wallets-kit@2.1.0` → `npm/@trezor/connect-plugin-stellar@9.2.3` → `npm/@trezor/blockchain-link@2.6.1` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: 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@socket.dev`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@trezor/blockchain-link@2.6.1`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm `@trezor/connect-common` under LicenseRef-T-RSL License: LicenseRef-T-RSL - The applicable license policy does not permit this license (5) (package/LICENSE.md) From: pnpm-lock.yaml → `npm/@creit.tech/stellar-wallets-kit@2.1.0` → `npm/@trezor/connect-plugin-stellar@9.2.3` → `npm/@trezor/connect-common@0.5.1` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: 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@socket.dev`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@trezor/connect-common@0.5.1`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm `@trezor/connect-plugin-stellar` under LicenseRef-T-RSL License: LicenseRef-T-RSL - The applicable license policy does not permit this license (5) (package/LICENSE.md) From: pnpm-lock.yaml → `npm/@creit.tech/stellar-wallets-kit@2.1.0` → `npm/@trezor/connect-plugin-stellar@9.2.6` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: 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@socket.dev`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@trezor/connect-plugin-stellar@9.2.6`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm `@trezor/connect-web` under LicenseRef-T-RSL License: LicenseRef-T-RSL - The applicable license policy does not permit this license (5) (package/LICENSE.md) From: pnpm-lock.yaml → `npm/@creit.tech/stellar-wallets-kit@2.1.0` → `npm/@trezor/connect-web@9.7.2` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: 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@socket.dev`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@trezor/connect-web@9.7.2`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm `@trezor/connect` under LicenseRef-T-RSL License: LicenseRef-T-RSL - The applicable license policy does not permit this license (5) (package/LICENSE.md) From: pnpm-lock.yaml → `npm/@creit.tech/stellar-wallets-kit@2.1.0` → `npm/@trezor/connect-plugin-stellar@9.2.3` → `npm/@trezor/connect@9.7.2` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: 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@socket.dev`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@trezor/connect@9.7.2`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm `@trezor/transport` under LicenseRef-T-RSL License: LicenseRef-T-RSL - The applicable license policy does not permit this license (5) (package/LICENSE.md) From: pnpm-lock.yaml → `npm/@creit.tech/stellar-wallets-kit@2.1.0` → `npm/@trezor/connect-plugin-stellar@9.2.3` → `npm/@trezor/transport@1.6.2` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: 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@socket.dev`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@trezor/transport@1.6.2`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm `@trezor/utils` under LicenseRef-T-RSL License: LicenseRef-T-RSL - The applicable license policy does not permit this license (5) (package/LICENSE.md) From: pnpm-lock.yaml → `npm/@creit.tech/stellar-wallets-kit@2.1.0` → `npm/@trezor/connect-plugin-stellar@9.2.3` → `npm/@trezor/utils@9.5.0` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: 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@socket.dev`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@trezor/utils@9.5.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm `@trezor/utxo-lib` under LicenseRef-T-RSL License: LicenseRef-T-RSL - The applicable license policy does not permit this license (5) (package/LICENSE.md) From: pnpm-lock.yaml → `npm/@creit.tech/stellar-wallets-kit@2.1.0` → `npm/@trezor/connect-plugin-stellar@9.2.3` → `npm/@trezor/utxo-lib@2.5.0` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: 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@socket.dev`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@trezor/utxo-lib@2.5.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm `next` Location: Package overview From: package.json → `npm/next@15.5.15` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: 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@socket.dev`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/next@15.5.15`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Copilot · 2026-03-18T21:34:57Z

@copilot fix the issue with frozen lock file in the test https://github.com/stellar/laboratory/actions/runs/23264179398/job/67653173536?pr=1958

...

Fixed in commit 911e80f. The pnpm-lock.yaml has been updated — the specifier now matches ^2.0.1 in package.json, so pnpm install --frozen-lockfile will pass in CI.

stellar-jenkins · 2026-03-18T21:37:18Z

Preview is available here:
http://laboratory-pr1958.previews.kube001.services.stellar-ops.com/

stellar-jenkins · 2026-03-18T21:39:08Z

Preview is available here:
http://laboratory-pr1958.previews.kube001.services.stellar-ops.com/

sagpatil · 2026-03-18T21:49:55Z

@copilot previous session had an error , please retry

Copilot · 2026-03-18T21:51:18Z

@copilot previous session had an error , please retry

The previous session successfully fixed the lockfile — pnpm-lock.yaml specifier is now ^2.0.1 (commit 911e80f). The current CI run 23268211655 has passed the "Install dependencies" step and is progressing through the build.

….5.14

…s.ts exists

Agent-Logs-Url: https://github.com/stellar/laboratory/sessions/ec93b2d1-d77c-48fd-a63c-7b88bb42e1b8

…-upgrade-stellar-wallet-kit Resolve merge conflicts: upgrade @creit.tech/stellar-wallets-kit to v2 on latest main

stellar-jenkins-ci · 2026-04-14T18:39:20Z

Preview is available here:
http://laboratory-pr1958.previews.kube001.services.stellar-ops.com/

Copilot

Pull request overview

Upgrades @creit.tech/stellar-wallets-kit to v2.0.1 and refactors wallet-connection/signing flows to match the library’s new static API, aiming to resolve a Next.js SSR hydration issue.

Changes:

Upgrade @creit.tech/stellar-wallets-kit to ^2.0.1 and bump next to 15.5.15.
Refactor wallet initialization/auth/signing to use StellarWalletsKit.init(), authModal(), and static signTransaction().
Make the network limits fetch script resilient to network failures by allowing a cached output file fallback.

Reviewed changes

Copilot reviewed 7 out of 8 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/hooks/useSignWithExtensionWallet.ts	Migrates signing flow from instance-based API to static `authModal()` + `signTransaction()`
src/helpers/getWalletKitNetwork.ts	Updates network enum mapping from `WalletNetwork` to `Networks`
src/components/WalletKit/WalletKitContextProvider.tsx	Reworks context to track kit initialization state and calls `StellarWalletsKit.init()`
src/components/WalletKit/ConnectWallet.tsx	Refactors connect/autoconnect flow to use `authModal()` and static kit methods
src/app/(sidebar)/smart-contracts/contract-explorer/components/InvokeContractForm.tsx	Updates signing to use static `StellarWalletsKit.signTransaction()`
scripts/fetch-network-limits.mjs	Adds cached output fallback when network fetch fails
package.json	Dependency upgrades for wallet kit + Next.js patch

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

sagpatil · 2026-04-15T17:37:16Z

@copilot can you fix the failing tests

sagpatil · 2026-04-15T17:37:43Z

@copilot apply changes based on the comments in this thread

Agent-Logs-Url: https://github.com/stellar/laboratory/sessions/a82cf766-e2a1-4931-b4fa-edc1949e0f40

Copilot · 2026-04-15T18:07:49Z

@copilot can you fix the failing tests

Fixed in commit c4cb1f6. The two failing tests were caused by v2 API changes:

signTransactionPage.test.ts — The wallet selection modal heading changed from "Connect a Wallet" to "Connect Wallet" in v2. Updated the assertion to match.
networkLimitsPage.test.ts — The dismissNetworkSettingsModal helper had a 1000ms timeout that was too short on slow CI runners. Increased it to 5000ms.

Also fixed a code review issue in useSignWithExtensionWallet.ts: replaced the useEffect-based isInProgress reset with a finally block so it always resets, including when authModal() resolves without an address.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

mainnet.sorobanrpc.com
- Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node scripts/fetch-network-limits.mjs (dns block)
- Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node scripts/fetch-network-limits.mjs ash ache/node/24.14.1/x64/bin/node i.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

stellar-jenkins-ci · 2026-04-15T18:12:05Z

Preview is available here:
http://laboratory-pr1958.previews.kube001.services.stellar-ops.com/

…t init Agent-Logs-Url: https://github.com/stellar/laboratory/sessions/e2f985f9-211f-4e43-a098-5c100b5aac33

Copilot · 2026-04-15T18:18:24Z

@copilot apply changes based on the comments in this thread

Applied in commit b7dfff2:

scripts/fetch-network-limits.mjs — The cache fallback now only triggers when all network fetches fail (tracked via successCount). If some networks succeed, the script continues to regenerate the file with partial data. The "unavailable for all networks" warning is now accurate.
src/components/WalletKit/WalletKitContextProvider.tsx — Removed the mount-only savedWallet state. The init effect now reads localStorageSavedWallet directly on each run, so when network.id changes it always picks up the wallet persisted for the active network (or falls back to an empty string). Removed unused savedWallet state, walletId context field, and SavedWallet import.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

mainnet.sorobanrpc.com
- Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node scripts/fetch-network-limits.mjs (dns block)
rpc-futurenet.stellar.org
- Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node scripts/fetch-network-limits.mjs (dns block)
soroban-testnet.stellar.org
- Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node scripts/fetch-network-limits.mjs (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

stellar-jenkins-ci · 2026-04-15T18:22:48Z

Preview is available here:
http://laboratory-pr1958.previews.kube001.services.stellar-ops.com/

- WalletKitContextProvider: add explicit null guard on savedWallet before checking savedWallet.network.id to prevent TypeError crash during hydration when both savedWallet and network.id are undefined - useSignWithExtensionWallet: change isInProgress from useState to useRef so setting it does not trigger re-renders, preventing the useCallback reference from changing and breaking the infinite authModal() loop in signTx useEffect

stellar-jenkins-ci · 2026-04-16T04:03:58Z

Preview is available here:
http://laboratory-pr1958.previews.kube001.services.stellar-ops.com/

sagpatil · 2026-04-16T04:53:20Z

@jeesunikim tests are passing now . can you please review

Initial plan

d2260d1

Copilot AI assigned Copilot and sagpatil Mar 18, 2026

github-project-automation bot added this to DevX Mar 18, 2026

github-project-automation bot moved this to Backlog (Not Ready) in DevX Mar 18, 2026

Copilot started work on behalf of sagpatil March 18, 2026 19:43 View session

Upgrade @creit.tech/stellar-wallets-kit to v2.0.1 with API migration

b857df3

Co-authored-by: sagpatil <1414227+sagpatil@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Upgrade Stellar Wallet Kits to the latest version~~ Upgrade @creit.tech/stellar-wallets-kit to v2.0.1 Mar 18, 2026

Copilot AI requested a review from sagpatil March 18, 2026 19:58

Copilot finished work on behalf of sagpatil March 18, 2026 19:58

sagpatil requested a review from jeesunikim March 18, 2026 21:26

Copilot started work on behalf of sagpatil March 18, 2026 21:29 View session

Copilot AI and others added 3 commits March 18, 2026 21:31

chore: sync pnpm-lock.yaml for stellar-wallets-kit v2.0.1

12a8eb4

Co-authored-by: sagpatil <1414227+sagpatil@users.noreply.github.com>

chore: sync pnpm-lock.yaml for stellar-wallets-kit v2.0.1

911e80f

Co-authored-by: sagpatil <1414227+sagpatil@users.noreply.github.com>

chore: restore husky pre-push hook

71ef0a4

Co-authored-by: sagpatil <1414227+sagpatil@users.noreply.github.com>

Copilot started work on behalf of sagpatil March 18, 2026 21:50 View session

Copilot finished work on behalf of sagpatil March 18, 2026 21:51

Initial plan

a164a2b

Copilot AI mentioned this pull request Apr 14, 2026

Resolve merge conflicts: upgrade @creit.tech/stellar-wallets-kit to v2 on latest main #2033

Merged

Copilot AI and others added 6 commits April 14, 2026 17:41

merge: incorporate latest changes from main

6bf9fdc

chore: regenerate pnpm-lock.yaml for stellar-wallets-kit v2 + next 15…

6b8a0b0

….5.14

fix: gracefully handle network fetch failure when cached networkLimit…

25fcd95

…s.ts exists

fix: improve network fallback message in fetch-network-limits.mjs

0e1ede1

Agent-Logs-Url: https://github.com/stellar/laboratory/sessions/ec93b2d1-d77c-48fd-a63c-7b88bb42e1b8

fix: bump next from 15.5.14 to 15.5.15 to patch DoS vulnerability

da58bf4

Agent-Logs-Url: https://github.com/stellar/laboratory/sessions/ec93b2d1-d77c-48fd-a63c-7b88bb42e1b8

Merge pull request #2033 from stellar/copilot/resolve-merge-conflicts…

010a294

…-upgrade-stellar-wallet-kit Resolve merge conflicts: upgrade @creit.tech/stellar-wallets-kit to v2 on latest main

sagpatil marked this pull request as ready for review April 14, 2026 18:36

Copilot AI review requested due to automatic review settings April 14, 2026 18:36

Copilot started reviewing on behalf of sagpatil April 14, 2026 18:36 View session

Copilot AI reviewed Apr 14, 2026

View reviewed changes

Comment thread scripts/fetch-network-limits.mjs Outdated

Comment thread src/hooks/useSignWithExtensionWallet.ts Outdated

Comment thread src/components/WalletKit/WalletKitContextProvider.tsx

Copilot started work on behalf of sagpatil April 15, 2026 17:37 View session

fix: fix e2e test failures for stellar-wallets-kit v2 modal changes

c4cb1f6

Agent-Logs-Url: https://github.com/stellar/laboratory/sessions/a82cf766-e2a1-4931-b4fa-edc1949e0f40

Copilot finished work on behalf of sagpatil April 15, 2026 18:08

Copilot started work on behalf of sagpatil April 15, 2026 18:08 View session

fix: address PR review feedback on network fallback and wallet contex…

b7dfff2

…t init Agent-Logs-Url: https://github.com/stellar/laboratory/sessions/e2f985f9-211f-4e43-a098-5c100b5aac33

Copilot finished work on behalf of sagpatil April 15, 2026 18:19

Conversation

Copilot AI commented Mar 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Breaking API Changes Addressed

Files Updated

I tried to connect to the following addresses, but was blocked by firewall rules:

Comments on the Issue (you are @copilot in this section)

Uh oh!

stellar-jenkins commented Mar 18, 2026

Uh oh!

stellar-jenkins commented Mar 18, 2026

Uh oh!

sagpatil commented Mar 18, 2026

Uh oh!

socket-security bot commented Mar 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security bot commented Mar 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI commented Mar 18, 2026

Uh oh!

stellar-jenkins commented Mar 18, 2026

Uh oh!

stellar-jenkins commented Mar 18, 2026

Uh oh!

sagpatil commented Mar 18, 2026

Uh oh!

Copilot AI commented Mar 18, 2026

Uh oh!

stellar-jenkins-ci bot commented Apr 14, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

sagpatil commented Apr 15, 2026

Uh oh!

sagpatil commented Apr 15, 2026

Uh oh!

Copilot AI commented Apr 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

stellar-jenkins-ci bot commented Apr 15, 2026

Uh oh!

Copilot AI commented Apr 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

stellar-jenkins-ci bot commented Apr 15, 2026

Uh oh!

stellar-jenkins-ci bot commented Apr 16, 2026

Uh oh!

sagpatil commented Apr 16, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Copilot AI commented Mar 18, 2026 •

edited

Loading

socket-security bot commented Mar 18, 2026 •

edited

Loading

socket-security bot commented Mar 18, 2026 •

edited

Loading

Copilot AI commented Apr 15, 2026 •

edited

Loading

Copilot AI commented Apr 15, 2026 •

edited

Loading