@solana/kit
v8.1.0 (2026-08-27)
Minor Changes
-
[
@solana/errors,@solana/transaction-messages] #19727d56e29Thanks @skyyycodes! - Validate compute unit limit and heap size when they are set on a transaction messagesetTransactionMessageComputeUnitLimit,setTransactionMessageHeapSizeandsetTransactionMessageConfignow reject values the runtime will not honor as written, throwingSOLANA_ERROR__TRANSACTION__COMPUTE_UNIT_LIMIT_OUT_OF_RANGEorSOLANA_ERROR__TRANSACTION__INVALID_HEAP_SIZEat 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:
decompileTransactionMessagestill returns messages carrying out-of-range values so that callers can inspect any transaction that reaches them. -
[
@solana/instruction-plans] #199595a2788Thanks @mcintyre94! - AddcreateTransactionPlanExecutorWithConcurrentLeavesto concurrently transform every transaction plan leaf while preserving the plan's result shape.
Patch Changes
-
[
@solana/codecs-core] #1970be30e32Thanks @koriyoshi2041! - FixtoArrayBufferslicing SharedArrayBuffer-backed views from a non-zero byte offset. -
[
@solana/codecs-data-structures] #1971c51b9f6Thanks @shin4141! - Preserve the literalfixedSizetype for single-field fixed-size struct codecs. -
[
@solana/codecs-strings] #19796852054Thanks @amilz! - FixedgetBase64Decoder()throwingRangeError: Maximum call stack size exceededin 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 singleString.fromCharCodecall. -
[
@solana/rpc,@solana/transaction-confirmation] #1994490ac9eThanks @matusbalascak! - Fix transaction confirmation and coalesced RPC request cancellation in environments where abort events have a null target.