Repository navigation
Transaction v1 (SIMD-0385) support, kit 8, 0.3.1 - #17
Merged
Merged
Conversation
0.3.0 was published from main before the transaction v1 work landed, so the v1 release needs a new version. Raises actions' peer range on core to ^0.3.1 and refreshes the lockfile after the kit 8 cherry-pick. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Makes
@pipeit/coreready for Solana transaction v1 (SIMD-0385, mainnet-active since 2026-09-15) and moves the workspace to@solana/kit8.3.0. Cherry-picked fromdeps/update-all-2026-05-28(edae8dea), which was left out of the PR #14 merge and the 0.3.0 release. Published as 0.3.1.TransactionBuilder,executePlanandcreateFlowacceptversion: 1. Default stays0.build()always resolves the compute unit limit and loaded accounts data size (simulation-based estimate with headroom, rounded to 32 KiB pages; no-rpc fallback with a warning) and converts the per-CU priority fee to total lamports.priorityFee: { strategy: 'fixed', lamports }sets the total directly (v1 only).getTransactionMessageSizeLimit;TRANSACTION_SIZE_LIMITis a deprecated alias of the legacy limit.TransactionVersionUnsupportedError/ResourceLimitEstimationErrorandtranslateVersionErrorfor kit's v1-related error codes, wired into diagnostics.executePlanreturns kit 8's{ signature }context; v1 + lookup tables is a type and runtime error.@pipeit/actions.@pipeit/example-next-js(Bun 1.4 rejects names with two slashes).Breaking changes
@solana/kit^7 → ^8 (and all@solana/*peers),@solana-program/compute-budget→ ^0.18.estimateComputeUnitLimitFactory,fillProvisorySetComputeUnitLimitInstruction,estimateAndUpdateProvisoryComputeUnitLimitFactory,createSetComputeUnitLimitInstruction,createSetComputeUnitPriceInstruction.executePlanresult context is{ signature }(kit 8) instead of the signed transaction.Verification
bun run typecheck,bun run lint,bun run buildclean.packages/core/scripts/v1-devnet-smoke.ts): a 1362-byte v1 transaction landed as version 1 with consumed CU under the estimate; fixed-CU, explicit-lamports-fee andexecutePlan({ version: 1 })scenarios all confirmed.🤖 Generated with Claude Code