build(deps): bump @solana/instructions from 2.3.0 to 6.0.0

[dependabot]

Bumps @solana/instructions from 2.3.0 to 6.0.0.

Release notes

Sourced from @​solana/instructions's releases.

v6.0.0

@​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.

... (truncated)

Commits

• 5e04dfc Version Packages (#1305)
• 235c747 Update instruction plans documentation guide (#1310)
• 608663c Make canary snapshot build use cache + concurrency (#1314)
• bd3d5f1 Add planType to distinguish between InstructionPlan, TransactionPlan an...
• 91cdb71 Remove deprecated function getAllSingleTransactionPlans (#1311)
• fc073dd Add documentation guide link to instruction plan README (#1308)
• 188c89e Replace @​template with @​typeParam in docblocks (#1307)
• 5f12df2 Pass mutable context to executeTransactionMessage callback (#1302)
• 5c810ac Reshape successful SingleTransactionPlanResult factories (#1293)
• fc58ba2 Extract base TransactionPlanResult context from generic TContext (#1292)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​solana/instructions since your current version.

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)

[dependabot]

Superseded by #495.