Upgrade to Kit v6

[mcintyre94]

Kit v6 is a breaking change, but mostly the changes are to do with instruction plans so nothing that affects connectorkit!

[vercel]

@mcintyre94 is attempting to deploy a commit to the Solana Foundation Team on Vercel.

A member of the Team first needs to authorize it.

[greptile-apps]

Greptile Overview

Greptile Summary

This PR upgrades @solana/kit from v5 to v6 across the example app and the connector/devtools packages, and refreshes pnpm-lock.yaml accordingly.

The main functional impact is dependency resolution: the lockfile now brings in @solana/*@6.0.1 packages that declare a Node engine requirement of >=20.18.0, which conflicts with the repo root package.json engine requirement of >=18.0.0.

Confidence Score: 3/5

• This PR is not safe to merge as-is due to a Node engine requirement mismatch introduced via the lockfile.
• While the code changes are limited to version bumps, the resolved v6 Solana packages require Node >=20.18.0, conflicting with the repo's declared Node >=18 engines and likely breaking installs/CI on Node 18.
• pnpm-lock.yaml (and repo root package.json engines setting)

Important Files Changed

Filename	Overview
examples/next-js/package.json	Bumps @solana/kit dependency from ^5.0.0 to ^6.0.0 for the Next.js example.
packages/connector/package.json	Bumps @solana/kit dependency from ^5.0.0 to ^6.0.0; ensure Node engine compatibility matches repo requirements.
packages/devtools/package.json	Bumps @solana/kit dependency from ^5.0.0 to ^6.0.0 in devtools package deps.
pnpm-lock.yaml	Updates lockfile for @solana/kit v6 resolution; introduces deps with Node engine >=20.18.0 which conflicts with repo's Node>=18 engines declaration.

Sequence Diagram

sequenceDiagram
  participant Dev as Developer/CI
  participant PNPM as pnpm
  participant Lock as pnpm-lock.yaml
  participant Reg as npm registry
  participant Kit as @solana/kit@6

  Dev->>PNPM: pnpm install
  PNPM->>Lock: Read resolved versions
  Lock-->>PNPM: @solana/kit ^6 resolves to 6.0.1
  PNPM->>Reg: Fetch @solana/*@6.x tarballs
  Reg-->>PNPM: Packages include engines node>=20.18.0
  PNPM-->>Dev: Install succeeds or fails
  Note over PNPM,Dev: Under Node < 20.18, engine checks may block install/runtime

Loading

[greptile-apps]

_{4 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Node engine mismatch

This lockfile now pulls in @solana/*@6.0.1 packages that declare engines: {node: '>=20.18.0'} (e.g. @solana/accounts@6.0.1). The repo root still declares "engines": {"node": ">=18.0.0"} in package.json, so installs/runs under Node 18 will fail (or be blocked depending on pnpm settings). Either bump the repo engine requirement to match Node 20.18+ or pin @solana/kit/related deps to versions compatible with Node 18.

[mcintyre94]

I've updated the Node engine to >= 20.18.0

Note that this is not a change in Kit v6, we've been using >= 20.18.0 since v2: anza-xyz/kit@1adf435

So this is an existing issue with the Node 18 support in this repo

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
connectorkit-playground	Ready	Preview, Comment	Feb 13, 2026 7:21am