Bump the solana-deps group across 1 directory with 2 updates

[dependabot]

Bumps the solana-deps group with 2 updates in the / directory: @solana-name-service/sns-sdk-kit and @solana/webcrypto-ed25519-polyfill.

Updates @solana-name-service/sns-sdk-kit from 0.10.0 to 0.10.1

Commits

• See full diff in compare view

Updates @solana/webcrypto-ed25519-polyfill from 6.9.0 to 7.0.0

Release notes

Sourced from @​solana/webcrypto-ed25519-polyfill's releases.

v7.0.0

@​solana/kit

v7.0.0 (2026-06-30)

Major Changes

• [@solana/codecs-data-structures] #1683 99667a1 Thanks @​oritwoen! - Align the return types of the union, predicate, and pattern-match codecs so that a fixed-size result is only exposed when every branch is fixed-size and of the same statically-known size. Branches whose sizes are unequal or not statically known now widen from FixedSize* to VariableSize* (when at least one branch is variable-size) or to a plain Encoder/Decoder/Codec (when the branches are fixed-size but their sizes are not statically comparable), matching what these codecs actually produce at runtime.

  This is a type-only change with no runtime impact, but it is breaking in two ways:

  • Return types change. Consumers that relied on the previous (unsound) fixed-size typing — e.g. reading .fixedSize, or passing the result where a FixedSize* is required — will need to adjust.
  • The predicate and pattern-match signatures changed. Their value/output type is now inferred from the branch encoders, decoders, or codecs rather than from an explicit type argument. Passing an explicit type argument no longer sets the branch domain: getPatternMatchEncoder<MyType>([...]) (and the decoder/codec equivalents) now fails to compile, and getPredicateEncoder<MyType>(...) silently degrades its return to a plain Encoder<MyType>. Instead, type the branch predicates' parameters (e.g. (value: MyType) => ...) and let the return type be inferred.

• [@solana/instruction-plans] #1723 069d56d Thanks @​mcintyre94! - Add configurable instruction-count limits to transaction planners and message packers, and default planned and packed transaction messages to 16 instructions. The planner limit applies to the final transaction message, including instructions returned by createTransactionMessage or added by onTransactionMessageUpdated, and can be overridden when creating a planner or for an individual planning call.

  This is useful because Solana limits transactions to 64 instructions, including inner instructions. Kit does not know how many inner instructions each instruction will require when executed. The default of 16 assumes an average of 3 additional inner instructions per top-level instruction.

  When a transaction message reaches this configured ceiling, the planner and message packer throw the new SOLANA_ERROR__INSTRUCTION_PLANS__MAX_INSTRUCTIONS_PER_TRANSACTION_EXCEEDED error rather than the SOLANA_ERROR__TRANSACTION__TOO_MANY_INSTRUCTIONS error reserved for the hard 64-instruction limit, so the configurable soft limit is distinguishable from the format-enforced one. Throws SOLANA_ERROR__INSTRUCTION_PLANS__INVALID_MAX_INSTRUCTIONS_PER_TRANSACTION is the configured max is invalid (not a positive integer, or greater than 64).

  Configure a maximum for every plan created by a transaction planner:

  const transactionPlanner = createTransactionPlanner({
      createTransactionMessage,
      maxInstructionsPerTransaction: 32,
  });

  Override the maximum for an individual planning request:

  const transactionPlan = await transactionPlanner(instructionPlan, {
      maxInstructionsPerTransaction: 8,
  });

  Override the maximum when packing a message directly:

  const packedTransactionMessage = messagePacker.packMessageToCapacity(transactionMessage, {
      maxInstructions: 32,
  });

  BREAKING CHANGES

  Transaction planners and message packers now default to 16 instructions per transaction. Plans and direct message packer calls that previously fit 17 to 64 top-level instructions in one transaction message may now be split into multiple transaction messages. Apps that depend on larger single-transaction plans can preserve the previous top-level instruction limit by configuring maxInstructionsPerTransaction: 64 on transaction planners or maxInstructions: 64 on direct message packer calls; the hard transaction-message limit of 64 top-level instructions still applies.

... (truncated)

Commits

• 58df993 Version Packages (#1768)
• cab6d7e Always include replacementBlockhash on simulateTransaction response (#1803)
• c5d8219 docs: add transaction introspection advanced guide (#1801)
• 2845b5c add typetest for getversion (#1797)
• e6dd38c add typetest for getEpochSchedule (#1796)
• 6947740 Remove deprecated getMinimumBalanceForRentExemption and createEmptyClient (#1...
• c3db383 Add a guide for reactive stores (#1782)
• acec0be Remove deprecated functions from ReactiveStreamStore (#1780)
• 1defa9c Add react guides to docs (#1779)
• 069d56d Add configurable max instructions per transaction to transaction planner (#1723)
• Additional commits viewable in compare view

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
good-wallet-v2	Ignored	Preview	Aug 4, 2026 10:45am