Bump @solana/codecs-strings from 7.1.1 to 8.2.0

[dependabot]

Bumps @solana/codecs-strings from 7.1.1 to 8.2.0.

Release notes

Sourced from @​solana/codecs-strings'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.

v8.1.0

@​solana/kit

v8.1.0 (2026-08-27)

Minor Changes

• [@solana/errors, @solana/transaction-messages] #1972 7d56e29 Thanks @​skyyycodes! - Validate compute unit limit and heap size when they are set on a transaction message

  setTransactionMessageComputeUnitLimit, setTransactionMessageHeapSize and setTransactionMessageConfig now reject values the runtime will not honor as written, throwing SOLANA_ERROR__TRANSACTION__COMPUTE_UNIT_LIMIT_OUT_OF_RANGE or SOLANA_ERROR__TRANSACTION__INVALID_HEAP_SIZE at the point the value is set. An invalid heap size fails the transaction on-chain; a compute unit limit above the maximum is instead clamped down by the runtime, so the transaction quietly runs with a budget other than the one requested. A compute unit limit must be an integer in the range [0, 1,400,000]; a heap size must be an integer multiple of 1 KiB between 32 KiB and 256 KiB inclusive.

  Decoding is unaffected: decompileTransactionMessage still returns messages carrying out-of-range values so that callers can inspect any transaction that reaches them.

• [@solana/instruction-plans] #1995 95a2788 Thanks @​mcintyre94! - Add createTransactionPlanExecutorWithConcurrentLeaves to concurrently transform every transaction plan leaf while preserving the plan's result shape.

Patch Changes

• [@solana/codecs-core] #1970 be30e32 Thanks @​koriyoshi2041! - Fix toArrayBuffer slicing SharedArrayBuffer-backed views from a non-zero byte offset.

• [@solana/codecs-data-structures] #1971 c51b9f6 Thanks @​shin4141! - Preserve the literal fixedSize type for single-field fixed-size struct codecs.

• [@solana/codecs-strings] #1979 6852054 Thanks @​amilz! - Fixed getBase64Decoder() throwing RangeError: Maximum call stack size exceeded in browser builds when decoding byte arrays larger than roughly 65KB. The bytes are now converted to a binary string in chunks rather than spread into a single String.fromCharCode call.

• [@solana/rpc, @solana/transaction-confirmation] #1994 490ac9e Thanks @​matusbalascak! - Fix transaction confirmation and coalesced RPC request cancellation in environments where abort events have a null target.

v8.0.0

@​solana/kit

v8.0.0 (2026-08-21)

Major Changes

• [@solana/instruction-plans] #1913 80368eb Thanks @​mcintyre94! - Stop writing to the execution context in createTransactionPlanExecutor

  The executeTransactionMessage callback can no longer return a Signature or a Transaction. Those return values were deprecated when the callback gained the ability to return the context that a successful result should carry, and they are now gone: that context, a complete TContext, is the only thing the callback returns. Nothing is written to it on your behalf.

... (truncated)

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)
• bb54243 Version Packages (#1980)
• 7d56e29 validate compute unit limit and heap size in transaction messages (#1972)
• c51b9f6 Preserve fixedSize for single-field struct codecs (#1971)
• Additional commits viewable 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[changeset-bot]

⚠️ No Changeset found

Latest commit: efd37c0

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

[dependabot]

Superseded by #120.