fix(deps): update dependency @solana/kit to v6 by renovate[bot] · Pull Request #289 · brave/token-lists

renovate · 2026-02-11T18:49:18Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@solana/kit (source)	`^2.1.0` → `^6.0.0`

Release Notes

anza-xyz/kit (@solana/kit)

`v6.7.0`

Compare Source

@solana/kit

v6.7.0 (2026-04-02)

Minor Changes

[@solana/plugin-core] #1509 2763d0c Thanks @lorisleiva! - Add createClient function that replaces createEmptyClient and accepts an optional initial value. The old createEmptyClient is preserved as a deprecated re-export.

`v6.6.0`

Compare Source

@solana/kit

v6.6.0 (2026-04-01)

Minor Changes

[@solana/errors, @solana/transaction-messages] #1496 7f02d23 Thanks @mcintyre94! - compileTransactionMessage now enforces four Solana protocol limits at compile time, throwing a typed SolanaError instead of silently producing a transaction that would be rejected by the network:
- More than 64 unique account addresses → SOLANA_ERROR__TRANSACTION__TOO_MANY_ACCOUNT_ADDRESSES
- More than 12 unique signer addresses → SOLANA_ERROR__TRANSACTION__TOO_MANY_SIGNER_ADDRESSES
- More than 64 instructions → SOLANA_ERROR__TRANSACTION__TOO_MANY_INSTRUCTIONS
- More than 255 accounts in a single instruction → SOLANA_ERROR__TRANSACTION__TOO_MANY_ACCOUNTS_IN_INSTRUCTION
All four error codes (and their context types / human-readable messages) are exported from @solana/errors.
[@solana/instruction-plans, @solana/transactions] #1499 742ffca Thanks @mcintyre94! - Add version-aware transaction size limits. Version 1 transactions now allow up to 4096 bytes, while legacy and v0 transactions continue to use the existing 1232-byte limit. Two new helper functions are exported from @solana/transactions: getTransactionSizeLimit for compiled Transaction objects, and getTransactionMessageSizeLimit for TransactionMessage objects.

The existing TRANSACTION_SIZE_LIMIT, TRANSACTION_PACKET_SIZE, and TRANSACTION_PACKET_HEADER constants are now deprecated in favour of getTransactionSizeLimit and will be removed in a future major version.
[@solana/plugin-core] #1480 9c4fd6e Thanks @mcintyre94! - Add withCleanup function to @solana/plugin-core. Plugin authors can use it to register teardown logic (e.g. closing connections or clearing timers) on a client, making it Disposable. If the client already implements Symbol.dispose, the new cleanup function is chained so both run on disposal.

Patch Changes

[@solana/instruction-plans] #1497 f055201 Thanks @mcintyre94! - The transaction planner now handles the four new transaction compilation constraint errors (TOO_MANY_ACCOUNT_ADDRESSES, TOO_MANY_SIGNER_ADDRESSES, TOO_MANY_INSTRUCTIONS, TOO_MANY_ACCOUNTS_IN_INSTRUCTION) gracefully. When adding an instruction to an existing candidate transaction would violate a constraint, the planner splits it into a new transaction — the same behaviour it already had for transactions that exceed the byte size limit. If even a fresh transaction cannot accommodate the instruction, the constraint error propagates to the caller.
[@solana/signers] #1492 0fa54a4 Thanks @lorisleiva! - Allow deduplicateSigners to handle structurally equivalent signers (e.g. two createNoopSigner calls with the same address) instead of throwing.

`v6.5.0`

Compare Source

@solana/kit

v6.5.0 (2026-03-19)

Minor Changes

[@solana/plugin-interfaces] #1486 10cb920 Thanks @lorisleiva! - Add ClientWithGetMinimumBalance plugin interface for computing the minimum balance required for an account. Implementations can use any strategy (e.g., RPC call, cached value) to provide this value through a uniform API.
[@solana/signers] #1487 9e05736 Thanks @lorisleiva! - Add partiallySignTransactionWithSigners, signTransactionWithSigners, and signAndSendTransactionWithSigners functions that accept a set of signers and a compiled Transaction directly, without requiring signers to be embedded in a transaction message. Also add assertContainsResolvableTransactionSendingSigner to validate that a set of signers contains an unambiguously resolvable sending signer. The existing transaction message helpers now delegate to these new functions internally.

Patch Changes

[@solana/kit] #1485 4a4c217 Thanks @lorisleiva! - Deprecated getMinimumBalanceForRentExemption. The minimum balance for an account is being actively reduced (see SIMD-0437) and is expected to become dynamic in future Solana upgrades (see SIMD-0194 and SIMD-0389). Use the getMinimumBalanceForRentExemption RPC method or a ClientWithGetMinimumBalance plugin instead. This function will be removed in v7.

`v6.4.0`

Compare Source

@solana/kit

v6.4.0 (2026-03-18)

Minor Changes

[@solana/kit] #1476 3e9e0a2 Thanks @lorisleiva! - Add compute unit limit estimation utilities: estimateComputeUnitLimitFactory, estimateAndSetComputeUnitLimitFactory, and fillTransactionMessageProvisoryComputeUnitLimit. These replace the external @solana-program/compute-budget estimation functions with Kit-native equivalents that work across all transaction versions.
[@solana/plugin-core] #1479 abeca1b Thanks @mcintyre94! - Add extendClient helper for plugin authors to merge client objects while preserving property descriptors (getters, symbol-keyed properties, and non-enumerable properties).

Plugin authors should migrate plugins to use this instead of spreading the input client.
```
- return { ...client, rpc };
+ return extendClient(client, { rpc });
```
[@solana/transaction-messages] #1472 084e92e Thanks @lorisleiva! - Add legacy and v0 transaction support to compute budget setters and getters. Priority fees are now handled by version-gated helpers: (get|set)TransactionMessagePriorityFeeLamports for v1 (total lamports) and (get|set)TransactionMessageComputeUnitPrice for legacy/v0 (micro-lamports per compute unit).
[@solana/wallet-account-signer] #1368 938ca94 Thanks @dpsi9! - Add functions to create Kit signers from Wallet Standard UiWalletAccount objects.

createSignerFromWalletAccount returns a TransactionSigner that can sign transactions using the solana:signTransaction and the solana:signAndSendTransaction features. At least one of these must be present in the wallet account. If the solana:signMessage feature is available, then this signer is also a MessageSigner.

There are also more specific helpers:
- createTransactionSignerFromWalletAccount(account, chain) returns a TransactionModifyingSigner that uses the wallet's solana:signTransaction feature.
- createTransactionSendingSignerFromWalletAccount(account, chain) returns a TransactionSendingSigner that uses the wallet's solana:signAndSendTransaction feature.
- createMessageSignerFromWalletAccount(account) returns a MessageModifyingSigner that uses the wallet's solana:signMessage feature.
These enable any wallet-standard wallet to be used as a Kit signer.

Patch Changes

[@solana/codecs-core, @solana/codecs-strings] #1391 27c3975 Thanks @holps-7! - Fix unnecessary array slicing/cloning when using negative offsets matching the array length.
[@solana/instruction-plans] #1470 896412d Thanks @lorisleiva! - Add trailing newline to multi-line error messages so that chained error causes render on their own line.
[@solana/kit] #1468 304436f Thanks @amilz! - Include source files in published packages so IDE "Go to Definition" navigates to TypeScript source instead of .d.ts type declarations

`v6.3.1`

Compare Source

@solana/kit

v6.3.1 (2026-03-12)

Patch Changes

[@solana/instruction-plans] #1464 a557a62 Thanks @lorisleiva! - Add the last 8 transaction log lines to the error message of SOLANA_ERROR__FAILED_TO_SEND_TRANSACTION and SOLANA_ERROR__FAILED_TO_SEND_TRANSACTIONS (when only one transaction failed).

`v6.3.0`

Compare Source

@solana/kit

v6.3.0 (2026-03-11)

Minor Changes

[@solana/errors, @solana/instruction-plans] #1444 f47d5cf Thanks @lorisleiva! - Enrich the SOLANA_ERROR__TRANSACTION__FAILED_WHEN_SIMULATING_TO_ESTIMATE_COMPUTE_LIMIT error context with the full simulation result (Omit<RpcSimulateTransactionResult, 'err'>) and add it to SolanaErrorCodeWithCause, aligning it with the SOLANA_ERROR__JSON_RPC__SERVER_ERROR_SEND_TRANSACTION_PREFLIGHT_FAILURE error.

`v6.2.0`

Compare Source

@solana/kit

v6.2.0 (2026-03-09)

Minor Changes

[@solana/codecs-data-structures] #1394 3f4c5f0 Thanks @mcintyre94! - Adds new functions getPatternMatchEncoder, getPatternMatchDecoder and getPatternMatchCodec.

These can be used to write an encoder that switches between any number of encoders based on the value being encoded, or a decoder that switches between any number of decoders based on the byte array being decoded.

For example for the encoder, the input is a list of [predicate, encoder] pairs. Each predicate is a function from the value being encoded to true/false. The encoder used is the first one where its predicate is true.
[@solana/wallet-account-signer] #1415 587ede3 Thanks @mcintyre94! - Add new @solana/wallet-account-signer package that will contain functions for converting from Wallet Standard accounts on Solana chains, to Kit Signer objects.

Patch Changes

[@solana/codecs-data-structures] #1420 5390602 Thanks @mcintyre94! - Enable pattern match encoder/codec to use type narrowing. This means that if your predicate narrows the type of the value, then the matching encoder only needs to handle the narrowed type.

This means that you can write, for example:
```
getPatternMatchEncoder<string | number>([
    [value => typeof value === 'string', {} as Encoder<string>],
    [value => typeof value === 'number', {} as Encoder<number>],
]);
```
[@solana/errors] #1440 0d0be3e Thanks @lorisleiva! - Append the instruction index to all instruction error messages (e.g. (instruction #1)) and add a human-readable message for unknown instruction errors.
[@solana/errors] #1432 7568a12 Thanks @lorisleiva! - Add SOLANA_ERROR__FAILED_TO_SEND_TRANSACTION and SOLANA_ERROR__FAILED_TO_SEND_TRANSACTIONS error codes for high-level transaction sending wrappers.
[@solana/errors] #1442 e33a65f Thanks @lorisleiva! - Remove stale $encodedData interpolation from the BORSH_IO_ERROR message. The encodedData context property was removed in v5.0.0 but the message template was not updated, causing the literal $encodedData to appear in the rendered error message.
[@solana/errors, @solana/instruction-plans] #1433 49c1195 Thanks @lorisleiva! - Add abortReason to the SOLANA_ERROR__INSTRUCTION_PLANS__FAILED_TO_EXECUTE_TRANSACTION_PLAN error context so consumers can access the abort reason when converting this error to higher-level error types.
[@solana/instruction-plans] #1435 98a8869 Thanks @lorisleiva! - Add createFailedToExecuteTransactionPlanError factory helper for custom transaction plan executor authors and refactor the built-in executor to use it.
[@solana/instruction-plans] #1434 79db829 Thanks @lorisleiva! - Add createFailedToSendTransactionError and createFailedToSendTransactionsError factory helpers that create high-level SolanaError instances from failed or canceled transaction plan results, with unwrapped simulation errors, preflight data, and logs in the error context.
[@solana/sysvars] #1428 b28b843 Thanks @datasalaryman! - use internals codecs dependencies

`v6.1.0`

Compare Source

@solana/kit

v6.1.0 (2026-02-16)

Minor Changes

[@solana/codecs-data-structures] #1363 70b1ed8 Thanks @mcintyre94! - Adds new functions getPredicateEncoder, getPredicateDecoder and getPredicateCodec.

These can be used to write an encoder that switches between two encoders based on the value being encoded, or a decoder that switches between two decoders based on the byte array being decoded.
[@solana/codecs-data-structures] #1369 7ce7545 Thanks @mcintyre94! - Allow passing a description to array and tuple encoders and codecs
- The ArrayCodecConfig is extended with an optional description
- The tuple encoder and codec now have an optional second argument, which is a new config object TupleCodecConfig with an optional description
- If either throws a SOLANA_ERROR__CODECS__INVALID_NUMBER_OF_ITEMS when encoding, the codecDescription field will be the description passed in the config. If no description is included then they will continue to default to array and tuple respectively.
[@solana/instruction-plans] #1334 1f6cd4b Thanks @lorisleiva! - Add parseInstructionOrTransactionPlanInput helper that converts flexible inputs (instruction plan input or transaction plan input) into an InstructionPlan or TransactionPlan
[@solana/instruction-plans] #1332 50010b5 Thanks @lorisleiva! - Add parseInstructionPlanInput helper that converts flexible inputs (single instruction, instruction plan, or array) into an InstructionPlan
[@solana/instruction-plans] #1333 33234f5 Thanks @lorisleiva! - Add parseTransactionPlanInput helper that converts flexible inputs (single transaction message, transaction plan, or array) into an TransactionPlan
[@solana/kit] #1356 da61429 Thanks @lorisleiva! - Add @solana/kit/program-client-core as a subpath export for @solana/program-client-core without changing root @solana/kit exports.
[@solana/plugin-interfaces] #1339 ee558a1 Thanks @lorisleiva! - Add @solana/plugin-interfaces package with TypeScript interfaces for building pluggable Solana clients. Includes ClientWithPayer, ClientWithAirdrop, ClientWithRpc, ClientWithRpcSubscriptions, ClientWithTransactionPlanning, and ClientWithTransactionSending interfaces.
[@solana/program-client-core] #1345 d3314a6 Thanks @lorisleiva! - Add new @solana/program-client-core package containing types and utilities for building Solana program clients. This is mainly used by the JavaScript Codama renderer to generate Kit-compatible program clients.

Patch Changes

[@solana/errors] #1344 3f711e1 Thanks @lorisleiva! - Add new error codes for program clients: SOLANA_ERROR__PROGRAM_CLIENTS__INSUFFICIENT_ACCOUNT_METAS, SOLANA_ERROR__PROGRAM_CLIENTS__UNRECOGNIZED_INSTRUCTION_TYPE, SOLANA_ERROR__PROGRAM_CLIENTS__FAILED_TO_IDENTIFY_INSTRUCTION, SOLANA_ERROR__PROGRAM_CLIENTS__UNEXPECTED_RESOLVED_INSTRUCTION_INPUT_TYPE, and SOLANA_ERROR__PROGRAM_CLIENTS__RESOLVED_INSTRUCTION_INPUT_MUST_BE_NON_NULL.
[@solana/errors] #1366 215027c Thanks @lorisleiva! - Add two new SolanaError codes for program clients: SOLANA_ERROR__PROGRAM_CLIENTS__UNRECOGNIZED_ACCOUNT_TYPE and SOLANA_ERROR__PROGRAM_CLIENTS__FAILED_TO_IDENTIFY_ACCOUNT.

`v6.0.1`

Compare Source

@solana/kit

v6.0.1 (2026-02-05)

Patch Changes

[@solana/kit, @solana/signers, @solana/transaction-messages] #1321 2d3296f Thanks @mcintyre94! - Fix a bug in the type of TransactionMessageWithSigners
[@solana/transaction-messages] #1318 a8a57ce Thanks @mcintyre94! - Fix bugs in types of setTransactionMessageLifetimeUsingBlockhash and setTransactionMessageLifetimeUsingDurableNonce

`v6.0.0`

Compare Source

@solana/kit

v6.0.0 (2026-02-04)

Major Changes

[@solana/instruction-plans] #1302 5f12df2 Thanks @lorisleiva! - The executeTransactionMessage callback in createTransactionPlanExecutor now receives a mutable context object as its first argument. This context can be incrementally populated during execution (e.g. with the latest transaction message, the compiled transaction, or custom properties) and is preserved in the resulting SingleTransactionPlanResult regardless of the outcome. If an error is thrown at any point in the callback, any attributes already saved to the context will still be available in the FailedSingleTransactionPlanResult, which is useful for debugging failures or building recovery plans.

The callback must now return either a Signature or a full Transaction object directly, instead of wrapping the result in an object.

BREAKING CHANGES

executeTransactionMessage callback signature changed. The callback now receives (context, message, config) instead of (message, config) and returns Signature | Transaction instead of { transaction: Transaction } | { signature: Signature }.
```
  const executor = createTransactionPlanExecutor({
-   executeTransactionMessage: async (message, { abortSignal }) => {
+   executeTransactionMessage: async (context, message, { abortSignal }) => {
      const transaction = await signTransactionMessageWithSigners(message);
+     context.transaction = transaction;
      await sendAndConfirmTransaction(transaction, { commitment: 'confirmed' });
-     return { transaction };
+     return transaction;
    }
  });
```
Custom context is now set via mutation instead of being returned. Previously, custom context was returned as part of the result object. Now, it must be set directly on the mutable context argument.
```
  const executor = createTransactionPlanExecutor({
-   executeTransactionMessage: async (message) => {
-     const transaction = await signAndSend(message);
-     return { transaction, context: { custom: 'value' } };
+   executeTransactionMessage: async (context, message) => {
+     context.custom = 'value';
+     const transaction = await signAndSend(message);
+     return transaction;
    }
  });
```
[@solana/instruction-plans] #1293 5c810ac Thanks @lorisleiva! - Reshape the successful SingleTransactionPlanResult factory functions. The successfulSingleTransactionPlanResult helper now accepts a context object (which must include a signature property) instead of a separate signature argument. A new successfulSingleTransactionPlanResultFromTransaction helper is introduced for the common case of creating a successful result from a full Transaction object.

BREAKING CHANGES

successfulSingleTransactionPlanResult renamed to successfulSingleTransactionPlanResultFromTransaction. If you were creating a successful result from a Transaction, update the function name.
```
- successfulSingleTransactionPlanResult(message, transaction)
+ successfulSingleTransactionPlanResultFromTransaction(message, transaction)
```
successfulSingleTransactionPlanResultFromSignature renamed to successfulSingleTransactionPlanResult with a new signature. The signature is no longer a separate argument — it must be included in the context object.
```
- successfulSingleTransactionPlanResultFromSignature(message, signature)
+ successfulSingleTransactionPlanResult(message, { signature })
```
```
- successfulSingleTransactionPlanResultFromSignature(message, signature, context)
+ successfulSingleTransactionPlanResult(message, { ...context, signature })
```
[@solana/instruction-plans] #1309 bd3d5f1 Thanks @lorisleiva! - Add a new planType property to all InstructionPlan, TransactionPlan, and TransactionPlanResult types to distinguish them from each other at runtime. This property is a string literal with the value 'instructionPlan', 'transactionPlan', or 'transactionPlanResult' respectively. It also adds new type guard functions that make use of that new property: isInstructionPlan, isTransactionPlan, and isTransactionPlanResult.

BREAKING CHANGES

InstructionPlan, TransactionPlan, and TransactionPlanResult type guards updated. All factories have been updated to add the new planType property but any custom instantiation of these types must be updated to include it as well.
```
  const myInstructionPlan: InstructionPlan = {
    kind: 'parallel',
    plans: [/* ... */],
+   planType: 'instructionPlan',
  };

  const myTransactionPlan: TransactionPlan = {
    kind: 'parallel',
    plans: [/* ... */],
+   planType: 'transactionPlan',
  };

  const myTransactionPlanResult: TransactionPlanResult = {
    kind: 'parallel',
    plans: [/* ... */],
+   planType: 'transactionPlanResult',
  };
```
[@solana/instruction-plans] #1311 91cdb71 Thanks @lorisleiva! - Remove deprecated function getAllSingleTransactionPlans

BREAKING CHANGES

getAllSingleTransactionPlans removed. Use flattenTransactionPlan instead.
```
- const singlePlans = getAllSingleTransactionPlans(transactionPlan);
+ const singlePlans = flattenTransactionPlan(transactionPlan);
```
[@solana/instruction-plans] #1276 2fbad6a Thanks @lorisleiva! - Reshape SingleTransactionPlanResult from a single object type with a status discriminated union into three distinct types: SuccessfulSingleTransactionPlanResult, FailedSingleTransactionPlanResult, and CanceledSingleTransactionPlanResult. This flattens the result structure so that status is now a string literal ('successful', 'failed', or 'canceled') and properties like context, error, and plannedMessage live at the top level of each variant.

Other changes include:
- Rename the message property to plannedMessage on all single transaction plan result types. This makes it clearer that this original planned message from the TransactionPlan, not the final message that was sent to the network.
- Move the context object from inside the status field to the top level of each result variant. All variants now carry a context — not just successful ones.
- Expand context attribute to optionally include message, signature, and transaction properties. These properties are meant to hold the actual TransactionMessage, Signature, and Transaction used when the transaction was sent to the network — which may differ from the originally plannedMessage.
- Remove the now-unused TransactionPlanResultStatus type.
- failedSingleTransactionPlanResult and canceledSingleTransactionPlanResult now accept an optional context parameter too.
BREAKING CHANGES

Accessing the status kind. Replace result.status.kind with result.status.
```
- if (result.status.kind === 'successful') { /* ... */ }
+ if (result.status === 'successful') { /* ... */ }
```
Accessing the signature. The signature has moved from result.status.signature to result.context.signature.
```
- const sig = result.status.signature;
+ const sig = result.context.signature;
```
Accessing the transaction. The transaction has moved from result.status.transaction to result.context.transaction.
```
- const tx = result.status.transaction;
+ const tx = result.context.transaction;
```
Accessing the error. The error has moved from result.status.error to result.error.
```
- const err = result.status.error;
+ const err = result.error;
```
Accessing the context. The context has moved from result.status.context to result.context.
```
- const ctx = result.status.context;
+ const ctx = result.context;
```
Accessing the message. The message property has been renamed to plannedMessage.
```
- const msg = result.message;
+ const msg = result.plannedMessage;
```
TransactionPlanResultStatus removed. Code that references this type must be updated to use the individual result variant types (SuccessfulSingleTransactionPlanResult, FailedSingleTransactionPlanResult, CanceledSingleTransactionPlanResult) or the SingleTransactionPlanResult union directly.
[@solana/transaction-messages] #1289 b82df4c Thanks @mcintyre94! - Remove the export of BaseTransactionMessage, which was previously deprecated. Use TransactionMessage instead.

Minor Changes

[@solana/instruction-plans] #1275 f8ef83e Thanks @lorisleiva! - Add missing TContext, TTransactionMessage and/or TSingle type parameters to TransactionPlanResult types and helper functions to better preserve type information through narrowing operations.

Patch Changes

[@solana/transaction-messages] #1287 f80b6de Thanks @mcintyre94! - Refactor compressTransactionMessageUsingAddressLookupTables to not use BaseTransactionMessage
[@solana/transaction-messages] #1288 986a09c Thanks @mcintyre94! - Refactor transaction-messages package to stop using BaseTransactionMessage

`v5.5.1`

Compare Source

@solana/kit

v5.5.1 (2026-01-28)

Patch Changes

[@solana/errors, @solana/instruction-plans] #1264 d957526 Thanks @lorisleiva! - Exports missing helpers in errors and instruction-plans

`v5.5.0`

Compare Source

@solana/kit

v5.5.0 (2026-01-27)

Minor Changes

[@solana/errors, @solana/instruction-plans] #1253 b4f5897 Thanks @lorisleiva! - Add isX and assertIsX type guard helpers for instruction plans, transaction plans, and transaction plan results
[@solana/errors] #1260 08c9062 Thanks @mcintyre94! - Mark the cause deprecated for SOLANA_ERROR__INSTRUCTION_PLANS__FAILED_TO_EXECUTE_TRANSACTION_PLAN error
[@solana/errors, @solana/instruction-plans] #1254 ba3f186 Thanks @lorisleiva! - Add SuccessfulTransactionPlanResult type with isSuccessfulTransactionPlanResult and assertIsSuccessfulTransactionPlanResult type guards
[@solana/errors, @solana/instruction-plans] #1236 1cc0a31 Thanks @mcintyre94! - Add getFirstFailedSingleTransactionPlanResult, which you can use to get the first failed transaction plan result from a transaction plan result, or throw if none failed
[@solana/errors] #1230 6af7c15 Thanks @mcintyre94! - Add a function unwrapSimulationError, which will return the cause of an error if it is a simulation error. Otherwise it is returned unchanged.
[@solana/instruction-plans] #1245 f731129 Thanks @mcintyre94! - Add flattenInstructionPlan and flattenTransactionPlan functions, that can be used to remove the sequential/parallel structure from these plans. Deprecate getAllSingleTransactionPlans which is superseded by flattenTransactionPlan.
[@solana/instruction-plans] #1233 b174ed5 Thanks @lorisleiva! - Add everyInstructionPlan, everyTransactionPlan and everyTransactionPlanResult functions that can be used to ensure a given predicate holds for all nodes inside their respective plan structures.
[@solana/instruction-plans] #1247 ea97d43 Thanks @mcintyre94! - Add a new function appendTransactionMessageInstructionPlan that can be used to add the instructions from an instruction plan to a transaction message
[@solana/instruction-plans] #1243 60e8c45 Thanks @lorisleiva! - Add transformInstructionPlan, transformTransactionPlan and transformTransactionPlanResult helpers for bottom-up transformation of instruction plan trees.
[@solana/instruction-plans] #1235 a47e441 Thanks @lorisleiva! - Add passthroughFailedTransactionPlanExecution helper function that wraps a transaction plan execution promise to return a TransactionPlanResult even on execution failure. This allows handling execution results in a unified way without try/catch.
[@solana/instruction-plans] #1232 589d761 Thanks @mcintyre94! - Add findInstructionPlan, findTransactionPlan and findTransactionPlanResult functions that can be used to find the plan matching a given predicate

Patch Changes

[@solana/instruction-plans] #1256 cccea6f Thanks @mcintyre94! - Fix a bug where a message packer that requires multiple iterations is not correctly added when forced to fit in a single transaction, even if it can fit
[@solana/kit] #1234 7e0377b Thanks @mcintyre94! - Fix a race condition in sendAndConfirmDurableNonceTransactionFactory
[@solana/react] #1210 56433e9 Thanks @rajgoesout! - Return immediately when passing empty array of transactions to useSignTransactions and useSignAndSendTransactions

`v5.4.0`

Compare Source

@solana/kit

v5.4.0 (2026-01-13)

Minor Changes

[@solana/accounts] #1152 fb1c576 Thanks @rajgoesout! - Include program + type when available in fetchJsonParsedAccount
[@solana/react] #1154 fec04ae Thanks @ningthoujamSwamikumar! - Add a context provider <SelectedWalletAccountContext> and useSelectedWalletAccount to persist a selected wallet account
[@solana/react] #1105 a301da8 Thanks @rajgoesout! - Add useSignTransactions and useSignAndSendTransactions hooks that you can use to send multiple transactions to a connected wallet.

Patch Changes

[@solana/accounts, @solana/addresses, @solana/assertions, @solana/codecs, @solana/codecs-core, @solana/codecs-data-structures, @solana/codecs-numbers, @solana/codecs-strings, @solana/compat, @solana/errors, @solana/fast-stable-stringify, @solana/functional, @solana/instruction-plans, @solana/instructions, @solana/keys, @solana/kit, @solana/nominal-types, @solana/offchain-messages, @solana/options, @solana/plugin-core, @solana/programs, @solana/promises, @solana/rpc, @solana/rpc-api, @solana/rpc-graphql, @solana/rpc-parsed-types, @solana/rpc-spec, @solana/rpc-spec-types, @solana/rpc-subscriptions, @solana/rpc-subscriptions-api, @solana/rpc-subscriptions-channel-websocket, @solana/rpc-subscriptions-spec, @solana/rpc-transformers, @solana/rpc-transport-http, @solana/rpc-types, @solana/signers, @solana/subscribable, @solana/sysvars, @solana/transaction-confirmation, @solana/transaction-messages, @solana/transactions, @solana/webcrypto-ed25519-polyfill] #1187 f5f89eb Thanks @mcintyre94! - Make Typescript peer dependency optional + reduce required version to ^5
[@solana/errors, @solana/rpc-transformers] #1186 189de37 Thanks @mcintyre94! - Fix type of error in sendTransaction preflight error

Some fields in RpcSimulateTransactionResult were incorrectly typed as number when they should have been bigint. At runtime these were bigint because of a bug.

At runtime all numeric fields in RpcSimulateTransactionResult were a bigint, but those typed as number are now correct.
[@solana/react] #1199 9bde4d7 Thanks @rajgoesout! - Correct featureName in signTransaction error

`v5.3.0`

Compare Source

@solana/kit

v5.3.0 (2026-01-07)

Minor Changes

[@solana/kit] #1065 fafa52f Thanks @rajgoesout! - Add local rent exemption calculator

`v5.2.0`

Compare Source

@solana/kit

v5.2.0 (2026-01-07)

Minor Changes

[@solana/instruction-plans, @solana/kit, @solana/signers, @solana/transaction-messages, @solana/transactions] #1139 6dbaf66 Thanks @mcintyre94! - Return more precise types from transaction message functions

Deprecate BaseTransactionMessage in favour of TransactionMessage
[@solana/kit, @solana/plugin-core] #1113 b1937c7 Thanks @lorisleiva! - Add new @solana/plugin-core package enabling us to create modular Kit clients that can be extended with plugins.

Patch Changes

[@solana/codecs-core] #1115 c391a44 Thanks @steveluscher! - Created a function that gives you a non-shared ArrayBuffer given any kind of Uint8Array
[@solana/codecs-core, @solana/codecs-numbers, @solana/codecs-strings, @solana/compat, @solana/keys] #1116 109c78e Thanks @steveluscher! - Any SharedArrayBuffer that gets passed to a crypto operation like signBytes or verifySignature will now be copied as non-shared. Crypto operations like sign and verify reject SharedArrayBuffers otherwise
[@solana/errors, @solana/instruction-plans] #1155 b80b092 Thanks @lorisleiva! - Throw early when the default transaction plan executor encounters a non-divisible transaction plan.
[@solana/rpc-subscriptions-channel-websocket] #1163 7d5a57c Thanks @lorisleiva! - Node users no longer need to manually install ws. Browser builds remain unaffected as conditional exports ensure ws is never bundled for browser environments.

`v5.1.0`

Compare Source

@solana/kit

v5.1.0 (2025-12-12)

Minor Changes

[@solana/errors, @solana/kit, @solana/offchain-messages] #880 becf5f6 Thanks @steveluscher! - Added codecs for encoding and decoding Solana Offchain Messages (see https://redirect.github.com/solana-foundation/SRFCs/discussions/3)
[@solana/errors, @solana/kit, @solana/offchain-messages] #984 32214f5 Thanks @steveluscher! - Added the capability to sign Solana Offchain Messages using a CryptoKey
[@solana/instruction-plans] #1044 e64a9b2 Thanks @mcintyre94! - Add a function to summarize a TransactionPlanResult
[@solana/instruction-plans] #1035 2bd0bc2 Thanks @mcintyre94! - Add a function to flatten a transaction plan result
[@solana/instruction-plans] #1056 a0c394b Thanks @lorisleiva! - Accept any Error object in failed SingleTransactionPlanResult
[@solana/instruction-plans] #1043 5c1f9e5 Thanks @mcintyre94! - Make Transaction optional in successful transaction plan result + add signature

Patch Changes

[@solana/addresses, @solana/codecs-core, @solana/offchain-messages, @solana/react, @solana/transactions] #1040 32b13a8 Thanks @OrmEmbaar! - Add a function called bytesEqual to codecs-core that you can use to compare two byte arrays for equality.
[@solana/codecs-strings, @solana/kit] #999 d7f5a0c Thanks @tmm! - Some npm packages are needed for specific runtimes only (eg. React Native, Node). To prevent package managers from unconditionally installing these packages when they have auto-install-peers enabled, we are marking them as optional in peerDependenciesMeta. When running in React Native, be sure to explicitly install fastestsmallesttextencoderdecoder. When running in Node, be sure to explicitly install ws. When using @solana/react, we will presume that you have already installed react.
[@solana/rpc] #1028 eb49ed7 Thanks @mcintyre94! - Add a type SolanaRpcApiFromClusterUrl
[@solana/rpc-api] #978 c97df88 Thanks @nonergodic! - Expanded the type of several RPC inputs to accept readonly arrays of values
[@solana/transaction-confirmation] #1003 [18e7e2c](https://redirect.github.com/anza-xyz/kit/commit/18e7e2c9d9013be6223932398f40cbc276c4a0e9

Configuration

📅 Schedule: (UTC)

Branch creation
- At any time (no schedule defined)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate bot requested a review from onyb as a code owner February 11, 2026 18:49

renovate bot force-pushed the renovate/solana-kit-6-x branch from d53adc5 to 25309bd Compare February 12, 2026 15:47

renovate bot force-pushed the renovate/solana-kit-6-x branch from 25309bd to 8c6de26 Compare February 23, 2026 22:59

renovate bot force-pushed the renovate/solana-kit-6-x branch from 8c6de26 to a20c0bb Compare March 5, 2026 19:12

renovate bot force-pushed the renovate/solana-kit-6-x branch 4 times, most recently from 393c6d3 to 78d98ac Compare March 19, 2026 17:06

renovate bot force-pushed the renovate/solana-kit-6-x branch 2 times, most recently from d785ad6 to 408a832 Compare March 26, 2026 18:59

renovate bot force-pushed the renovate/solana-kit-6-x branch 2 times, most recently from 9fc7aa6 to dc534e1 Compare April 8, 2026 19:47

fix(deps): update dependency @solana/kit to v6

6566355

renovate bot force-pushed the renovate/solana-kit-6-x branch from dc534e1 to 6566355 Compare April 9, 2026 18:03

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update dependency @solana/kit to v6#289

fix(deps): update dependency @solana/kit to v6#289
renovate[bot] wants to merge 1 commit intomainfrom
renovate/solana-kit-6-x

renovate bot commented Feb 11, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate bot commented Feb 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v6.7.0 (2026-04-02)

Minor Changes

v6.6.0 (2026-04-01)

Minor Changes

Patch Changes

v6.5.0 (2026-03-19)

Minor Changes

Patch Changes

v6.4.0 (2026-03-18)

Minor Changes

Patch Changes

v6.3.1 (2026-03-12)

Patch Changes

v6.3.0 (2026-03-11)

Minor Changes

v6.2.0 (2026-03-09)

Minor Changes

Patch Changes

v6.1.0 (2026-02-16)

Minor Changes

Patch Changes

v6.0.1 (2026-02-05)

Patch Changes

v6.0.0 (2026-02-04)

Major Changes

Minor Changes

Patch Changes

v5.5.1 (2026-01-28)

Patch Changes

v5.5.0 (2026-01-27)

Minor Changes

Patch Changes

v5.4.0 (2026-01-13)

Minor Changes

Patch Changes

v5.3.0 (2026-01-07)

Minor Changes

v5.2.0 (2026-01-07)

Minor Changes

Patch Changes

v5.1.0 (2025-12-12)

Minor Changes

Patch Changes

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate bot commented Feb 11, 2026 •

edited

Loading