Skip to content

Deps/update all 2026 05 28 - #14

Open
stevesarmiento wants to merge 13 commits into
mainfrom
deps/update-all-2026-05-28
Open

Deps/update all 2026 05 28#14
stevesarmiento wants to merge 13 commits into
mainfrom
deps/update-all-2026-05-28

Conversation

@stevesarmiento

Copy link
Copy Markdown
Owner

No description provided.

- replace pnpm workspace files with `bun.lock` and Bun workspace config
- update docs, ignore files, and scripts to use Bun commands
- refresh ESLint and package/tooling dependencies across packages
@vercel

vercel Bot commented May 28, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
pipeit-next-js Ready Ready Preview Aug 19, 2026 12:04am

Request Review

- Add new Phoenix and Flash InstructionPlan factories
- Update docs and lockfile for the new actions package deps
- Refresh build config for the expanded actions bundle
- Remove unnecessary memoization in pipeline visualization
- Keep motion effects aligned with prefers-reduced-motion
- Include only fastlane runtime files in Next.js tracing
- Exclude build and source directories that Vercel cannot package
- Update Turbo inputs for bunfig and Next config changes
- @solana/* kit packages 6.9.0 -> 6.10.0 across core, actions, next-js
- @solana/web3.js pin 1.98.2 -> 1.98.4 in actions (dedupes with next-js)
- @ellipsis-labs/rise 0.4.17 -> 0.4.62, flash-sdk 15.16.14 -> 15.17.2
- next-js: radix-ui, tanstack query, xyflow, motion, lucide, zustand, tailwind patch/minor bumps
- tooling: eslint 10.6.0, prettier 3.9.4, turbo 2.10.3, typescript-eslint 8.62.1, vitest 4.1.9, @napi-rs/cli 3.7.2

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Bump all @solana/* kit packages ^6.x -> ^7.0.0 across core, actions,
  next-js (deps, devDeps, and peerDependencies)
- Add root override forcing @solana/kit ^7.0.0: the @solana-program/*
  clients (compute-budget, system, token) still peer on kit ^6.x, which
  would otherwise nest a second kit 6 copy and break types. Their
  codegen'd APIs are unaffected by kit 7 breaking changes.
- Bump @solana-program/compute-budget ^0.15 -> ^0.16 and
  @solana-program/token ^0.13 -> ^0.14
- Expose maxInstructionsPerTransaction pass-through on executePlan:
  kit 7 planners default to 16 instructions per transaction (was 64);
  callers can restore the old ceiling with { maxInstructionsPerTransaction: 64 }

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- package.json conflicts: kept branch versions (strictly newer — kit 7,
  eslint 10.6, turbo 2.10, typescript 6, vitest 4 vs main's kit 6 stack)
- pnpm-lock.yaml: removed (branch migrated to Bun; bun.lock is canonical)
- main's pnpm override (globalthis -> @ungap/global-this) was NOT ported:
  es-iterator-helpers in the current eslint stack calls
  require('globalthis')() as a factory, which @ungap/global-this does not
  provide, breaking lint
- main's code changes (kit executor/TransactionPlanResult migration) were
  already present on this branch and auto-merged cleanly

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Add shared test helpers and coverage for flash and phoenix plan builders
- Clarify client reuse, onboarding prerequisites, and API behavior in README
- Bump @pipeit/actions to 0.2.0
- Avoid 12.2.0+ due to unconditional `tokio::net::UnixStream` import
- Keep Windows builds working until upstream fix lands
stevesarmiento and others added 2 commits August 18, 2026 17:03
Migrates compute budget handling to Kit v7's version-agnostic APIs so the
same code paths work once v1 transaction construction is un-gated upstream,
and fixes a live type hazard introduced by the Kit v7 bump.

- lookup-tables/compress.ts: guard on `version === 0` instead of
  `!== 'legacy'`. Kit v7 widened TransactionMessage to include v1, which
  does not support address lookup tables, so the old `Exclude<..., legacy>`
  cast would have silently compressed v1 messages into lookup metas that
  cannot be encoded.
- builder: replace hand-rolled compute budget instruction encoders with
  Kit's setTransactionMessageComputeUnitLimit / ComputeUnitPrice /
  LoadedAccountsDataSizeLimit. These are version-agnostic (instructions on
  legacy/v0, message config on v1). Applied before user instructions, so
  the wire order [limit, price, LADS, ...user] is byte-identical; new
  byte-level tests lock this in.
- builder + execute-plan: move from @solana-program/compute-budget's
  CU-only estimators (deprecated in Kit v7) to
  fillTransactionMessageProvisoryResourceLimits /
  estimateResourceLimitsFactory / estimateAndSetResourceLimitsFactory.
- Add `loadedAccountsDataSizeLimit?: number` to TransactionBuilderConfig,
  default absent. Not injected automatically: on legacy/v0 it costs a whole
  compute budget instruction of transaction space for a limit that is
  rarely binding.
- Add `SupportedTransactionVersion` (0 | 'legacy') mirroring Kit 7.0.0's
  own constructor gate, used everywhere version is typed. This is the
  single widening point for when Kit allows createTransactionMessage to
  produce v1.

Behavior changes:
- The documented `buffer` option on the simulate CU strategy was never
  applied; it now is (default 1.1). Simulate-strategy compute unit limits
  are ~10% higher, with a small corresponding priority fee cost.
- The buffer is also applied to estimated loadedAccountsDataSizeLimit.
  Simulation reflects current chain state: an account that exists costs
  more to load than one that does not, so an exact limit can fail if
  anyone funds the account before the transaction lands. Kit is
  unopinionated here and does not pad. No effect until v1, since Kit only
  applies LADS estimates to v1 messages.
- Simulation failures now surface Kit's
  SOLANA_ERROR__TRANSACTION__FAILED_WHEN_SIMULATING_TO_ESTIMATE_RESOURCE_LIMITS
  instead of @solana-program/compute-budget's error codes.

No public API removals: createSetComputeUnitLimitInstruction and
createSetComputeUnitPriceInstruction are now deprecated wrappers over the
generated builders with byte-identical output.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
- Drop the solana-sdk dependency in favor of solana-signature. The crate
  only ever used solana_sdk::signature::Signature, and the lock already
  resolved a single shared solana-signature 3.x, so type identity with
  solana-client's APIs is preserved. Prunes a large unused subtree from
  Cargo.lock.
- Delete the vendored protobuf-src copy. Its [patch.crates-io] entry was
  removed earlier on this branch (yellowstone-grpc-proto 12.4 pulls
  protoc-bin-vendored directly), leaving the directory unreferenced.
- Bump 0.1.6 -> 0.1.7 in Cargo.toml and package.json; index.js bindings
  regenerated by napi build.

Kept deliberately:
- yellowstone-grpc-client stays pinned at =12.1.0. Upstream fix for the
  unconditional tokio::net::UnixStream import that breaks Windows builds
  (rpcpool/yellowstone-grpc#742) is still open as of 2026-08-11, and the
  latest 13.x releases do not carry it.
- Solana crates stay at the 4.0.x lock resolution. Updating to 4.1.2 does
  not compile: solana-transaction-status-client-types 4.1.2 requires
  wincode 0.5 while solana-address 2.7.0 moved to wincode 0.6, producing
  duplicate-trait errors on VersionedTransaction. Revisit once upstream
  converges on one wincode major.

Verified with cargo check, a release napi build, and test.mjs run against
the rebuilt darwin-arm64 binary (7/7 passing).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant