build(deps): bump the solana-kit group with 5 updates

[dependabot]

Bumps the solana-kit group with 5 updates:

Package	From	To
@solana/addresses	8.1.0	8.2.0
@solana/codecs	8.1.0	8.2.0
@solana/kit	8.1.0	8.2.0
@solana/instructions	8.1.0	8.2.0
@solana/accounts	8.1.0	8.2.0

Updates @solana/addresses from 8.1.0 to 8.2.0

Release notes

Sourced from @​solana/addresses's releases.

v8.2.0

@​solana/kit

v8.2.0 (2026-08-29)

Minor Changes

• [@solana/instruction-plans] #2013 26edd3b Thanks @​mcintyre94! - Align createTransactionPlanExecutorWithConcurrentLeaves with createTransactionPlanExecutor by giving both the same TransactionPlanExecutorConfig. Its executeTransactionMessage callback now receives a mutable per-leaf context object and returns the context of a successful result, instead of building a whole SingleTransactionPlanResult itself. The executor builds the results: on success it merges the returned context over the stored one, and when the callback throws — or the abort signal fires before it settles — it preserves the stored context on the failed result, matching the partial-context behaviour of createTransactionPlanExecutor. The ConcurrentLeafTransactionPlanExecutorConfig type is removed. This is a breaking change to the createTransactionPlanExecutorWithConcurrentLeaves API introduced in 8.1.0.

Patch Changes

• [@solana/signers] #2006 d385ce3 Thanks @​amilz! - Relaxed the parameter type of the signer type guards (isMessagePartialSigner, isTransactionSigner, isKeyPairSigner, their siblings, and the assertIs* variants) so that class instances implementing a signer interface can be passed without casts. The guards now accept any TValue extends { address: Address } and narrow to TValue & Signer, whereas the previous parameter type required an implicit index signature, which TypeScript never grants to class instances.

Commits

• b0a9749 Version Packages (#2015)
• d385ce3 fix: accept class-based signers in @solana/signers type guards (#2006)
• 26edd3b Unify the concurrent leaf executor's callback contract with `createTransactio...
• ceba283 Bump start-server-and-test from 3.0.11 to 3.0.12 (#2009)
• d04c874 Also run preview-docs in the merge queue (#2008)
• fc32b73 Bump @​tanstack/react-query from 5.101.4 to 5.102.3 in /docs (#2011)
• 584422f Update docs CI so that it can be required (#2003)
• See full diff in compare view

Updates @solana/codecs from 8.1.0 to 8.2.0

Release notes

Sourced from @​solana/codecs's releases.

v8.2.0

@​solana/kit

v8.2.0 (2026-08-29)

Minor Changes

• [@solana/instruction-plans] #2013 26edd3b Thanks @​mcintyre94! - Align createTransactionPlanExecutorWithConcurrentLeaves with createTransactionPlanExecutor by giving both the same TransactionPlanExecutorConfig. Its executeTransactionMessage callback now receives a mutable per-leaf context object and returns the context of a successful result, instead of building a whole SingleTransactionPlanResult itself. The executor builds the results: on success it merges the returned context over the stored one, and when the callback throws — or the abort signal fires before it settles — it preserves the stored context on the failed result, matching the partial-context behaviour of createTransactionPlanExecutor. The ConcurrentLeafTransactionPlanExecutorConfig type is removed. This is a breaking change to the createTransactionPlanExecutorWithConcurrentLeaves API introduced in 8.1.0.

Patch Changes

• [@solana/signers] #2006 d385ce3 Thanks @​amilz! - Relaxed the parameter type of the signer type guards (isMessagePartialSigner, isTransactionSigner, isKeyPairSigner, their siblings, and the assertIs* variants) so that class instances implementing a signer interface can be passed without casts. The guards now accept any TValue extends { address: Address } and narrow to TValue & Signer, whereas the previous parameter type required an implicit index signature, which TypeScript never grants to class instances.

Commits

• b0a9749 Version Packages (#2015)
• d385ce3 fix: accept class-based signers in @solana/signers type guards (#2006)
• 26edd3b Unify the concurrent leaf executor's callback contract with `createTransactio...
• ceba283 Bump start-server-and-test from 3.0.11 to 3.0.12 (#2009)
• d04c874 Also run preview-docs in the merge queue (#2008)
• fc32b73 Bump @​tanstack/react-query from 5.101.4 to 5.102.3 in /docs (#2011)
• 584422f Update docs CI so that it can be required (#2003)
• See full diff in compare view

Updates @solana/kit from 8.1.0 to 8.2.0

Release notes

Sourced from @​solana/kit's releases.

v8.2.0

@​solana/kit

v8.2.0 (2026-08-29)

Minor Changes

• [@solana/instruction-plans] #2013 26edd3b Thanks @​mcintyre94! - Align createTransactionPlanExecutorWithConcurrentLeaves with createTransactionPlanExecutor by giving both the same TransactionPlanExecutorConfig. Its executeTransactionMessage callback now receives a mutable per-leaf context object and returns the context of a successful result, instead of building a whole SingleTransactionPlanResult itself. The executor builds the results: on success it merges the returned context over the stored one, and when the callback throws — or the abort signal fires before it settles — it preserves the stored context on the failed result, matching the partial-context behaviour of createTransactionPlanExecutor. The ConcurrentLeafTransactionPlanExecutorConfig type is removed. This is a breaking change to the createTransactionPlanExecutorWithConcurrentLeaves API introduced in 8.1.0.

Patch Changes

• [@solana/signers] #2006 d385ce3 Thanks @​amilz! - Relaxed the parameter type of the signer type guards (isMessagePartialSigner, isTransactionSigner, isKeyPairSigner, their siblings, and the assertIs* variants) so that class instances implementing a signer interface can be passed without casts. The guards now accept any TValue extends { address: Address } and narrow to TValue & Signer, whereas the previous parameter type required an implicit index signature, which TypeScript never grants to class instances.

Commits

• b0a9749 Version Packages (#2015)
• d385ce3 fix: accept class-based signers in @solana/signers type guards (#2006)
• 26edd3b Unify the concurrent leaf executor's callback contract with `createTransactio...
• ceba283 Bump start-server-and-test from 3.0.11 to 3.0.12 (#2009)
• d04c874 Also run preview-docs in the merge queue (#2008)
• fc32b73 Bump @​tanstack/react-query from 5.101.4 to 5.102.3 in /docs (#2011)
• 584422f Update docs CI so that it can be required (#2003)
• See full diff in compare view

Updates @solana/instructions from 8.1.0 to 8.2.0

Release notes

Sourced from @​solana/instructions's releases.

v8.2.0

@​solana/kit

v8.2.0 (2026-08-29)

Minor Changes

• [@solana/instruction-plans] #2013 26edd3b Thanks @​mcintyre94! - Align createTransactionPlanExecutorWithConcurrentLeaves with createTransactionPlanExecutor by giving both the same TransactionPlanExecutorConfig. Its executeTransactionMessage callback now receives a mutable per-leaf context object and returns the context of a successful result, instead of building a whole SingleTransactionPlanResult itself. The executor builds the results: on success it merges the returned context over the stored one, and when the callback throws — or the abort signal fires before it settles — it preserves the stored context on the failed result, matching the partial-context behaviour of createTransactionPlanExecutor. The ConcurrentLeafTransactionPlanExecutorConfig type is removed. This is a breaking change to the createTransactionPlanExecutorWithConcurrentLeaves API introduced in 8.1.0.

Patch Changes

• [@solana/signers] #2006 d385ce3 Thanks @​amilz! - Relaxed the parameter type of the signer type guards (isMessagePartialSigner, isTransactionSigner, isKeyPairSigner, their siblings, and the assertIs* variants) so that class instances implementing a signer interface can be passed without casts. The guards now accept any TValue extends { address: Address } and narrow to TValue & Signer, whereas the previous parameter type required an implicit index signature, which TypeScript never grants to class instances.

Commits

• b0a9749 Version Packages (#2015)
• d385ce3 fix: accept class-based signers in @solana/signers type guards (#2006)
• 26edd3b Unify the concurrent leaf executor's callback contract with `createTransactio...
• ceba283 Bump start-server-and-test from 3.0.11 to 3.0.12 (#2009)
• d04c874 Also run preview-docs in the merge queue (#2008)
• fc32b73 Bump @​tanstack/react-query from 5.101.4 to 5.102.3 in /docs (#2011)
• 584422f Update docs CI so that it can be required (#2003)
• See full diff in compare view

Updates @solana/accounts from 8.1.0 to 8.2.0

Release notes

Sourced from @​solana/accounts's releases.

v8.2.0

@​solana/kit

v8.2.0 (2026-08-29)

Minor Changes

• [@solana/instruction-plans] #2013 26edd3b Thanks @​mcintyre94! - Align createTransactionPlanExecutorWithConcurrentLeaves with createTransactionPlanExecutor by giving both the same TransactionPlanExecutorConfig. Its executeTransactionMessage callback now receives a mutable per-leaf context object and returns the context of a successful result, instead of building a whole SingleTransactionPlanResult itself. The executor builds the results: on success it merges the returned context over the stored one, and when the callback throws — or the abort signal fires before it settles — it preserves the stored context on the failed result, matching the partial-context behaviour of createTransactionPlanExecutor. The ConcurrentLeafTransactionPlanExecutorConfig type is removed. This is a breaking change to the createTransactionPlanExecutorWithConcurrentLeaves API introduced in 8.1.0.

Patch Changes

• [@solana/signers] #2006 d385ce3 Thanks @​amilz! - Relaxed the parameter type of the signer type guards (isMessagePartialSigner, isTransactionSigner, isKeyPairSigner, their siblings, and the assertIs* variants) so that class instances implementing a signer interface can be passed without casts. The guards now accept any TValue extends { address: Address } and narrow to TValue & Signer, whereas the previous parameter type required an implicit index signature, which TypeScript never grants to class instances.

Commits

• b0a9749 Version Packages (#2015)
• d385ce3 fix: accept class-based signers in @solana/signers type guards (#2006)
• 26edd3b Unify the concurrent leaf executor's callback contract with `createTransactio...
• ceba283 Bump start-server-and-test from 3.0.11 to 3.0.12 (#2009)
• d04c874 Also run preview-docs in the merge queue (#2008)
• fc32b73 Bump @​tanstack/react-query from 5.101.4 to 5.102.3 in /docs (#2011)
• 584422f Update docs CI so that it can be required (#2003)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[changeset-bot]

⚠️ No Changeset found

Latest commit: d0141a3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR