Skip to content

build(deps): bump @solana/instruction-plans from 7.0.0 to 8.1.0 - #779

Merged
github-actions[bot] merged 1 commit into
mainfrom
dependabot/npm_and_yarn/solana/instruction-plans-8.1.0
Aug 31, 2026
Merged

build(deps): bump @solana/instruction-plans from 7.0.0 to 8.1.0#779
github-actions[bot] merged 1 commit into
mainfrom
dependabot/npm_and_yarn/solana/instruction-plans-8.1.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 31, 2026

Copy link
Copy Markdown
Contributor

Bumps @solana/instruction-plans from 7.0.0 to 8.1.0.

Release notes

Sourced from @​solana/instruction-plans's releases.

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.

    const transactionPlanExecutor = createTransactionPlanExecutor({
      executeTransactionMessage: async (context, message) => {
        const transaction = await signTransactionMessageWithSigners(message);
        context.transaction = transaction;
    +   const signature = getSignatureFromTransaction(transaction);
        await sendAndConfirmTransaction(transaction, { commitment: 'confirmed' });
    -   return transaction;
    +   return { signature, transaction };
      },
    });

    The mutable context argument is still there, and still serves the failure path: whatever the callback stores on it before it throws is preserved in the resulting FailedSingleTransactionPlanResult. The two channels differ only in which outcome they feed. Mutating the context makes a value available to a failed result; returning it makes a value available to a successful one. On success the two are merged, with the returned value taking precedence, so a property stored but not returned is still reported.

... (truncated)

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Aug 31, 2026
@github-actions
github-actions Bot enabled auto-merge (squash) August 31, 2026 09:06
github-actions[bot]
github-actions Bot previously approved these changes Aug 31, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/solana/instruction-plans-8.1.0 branch from 4e9b2c9 to 1577ea7 Compare August 31, 2026 09:27
github-actions[bot]
github-actions Bot previously approved these changes Aug 31, 2026
Bumps [@solana/instruction-plans](https://github.com/anza-xyz/kit) from 7.0.0 to 8.1.0.
- [Release notes](https://github.com/anza-xyz/kit/releases)
- [Commits](anza-xyz/kit@v7.0.0...v8.1.0)

---
updated-dependencies:
- dependency-name: "@solana/instruction-plans"
  dependency-version: 8.1.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/solana/instruction-plans-8.1.0 branch from 1577ea7 to bc8c0ca Compare August 31, 2026 09:29
@github-actions
github-actions Bot merged commit d1f0192 into main Aug 31, 2026
24 checks passed
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/solana/instruction-plans-8.1.0 branch August 31, 2026 09:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants