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

[Copilot]

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]

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

[stellar-jenkins]

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

[sagpatil]

@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

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​creit.tech/​stellar-wallets-kit@​1.9.5 ⏵ 2.0.1	+2		-1	+7

View full report

[socket-security]

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 allow this license (4) (npm metadata) License: GPL-3.0 - the applicable license policy does not allow this license (4) (package/package.json) From: pnpm-lock.yaml → npm/@creit.tech/stellar-wallets-kit@2.0.1 → 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.

View full report

[Copilot]

@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]

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

[stellar-jenkins]

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

[sagpatil]

@copilot previous session had an error , please retry

[Copilot]

@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.