chore: migrate to TypeScript 7 - #428
Merged
Merged
Conversation
Bump typescript ^6.0.3 -> ^7.0.2 (the native Go compiler) across the root and all packages, and tsdown ^0.22.3 -> ^0.22.7 whose peer range now allows ^7 (pulls rolldown-plugin-dts 0.27.8, also TS7-aware). `tsc --noEmit` runs the native compiler as a drop-in for check:types; tsdown + oxc continue to handle bundling and isolated-declaration d.ts generation (the TS JS compiler API is not shipped in typescript@7, but it isn't needed on this path). pnpm auto-added supply-chain (minimumReleaseAge) exclusions for the new toolchain packages. Verified locally: check, build, check:types, and test all pass on the native compiler. Building identical source on TS6 vs TS7 produces byte- identical published .d.ts (modulo comment/whitespace formatting) and semantically identical JS, so there is no consumer-facing impact. Tooling-only devDependency change: no changeset (devDependencies are stripped from published packages).
|
Merged
chybisov
force-pushed
the
chore/typescript-7
branch
from
July 13, 2026 11:17
80dacde to
5b26a72
Compare
# Conflicts: # package.json # packages/sdk-provider-bitcoin/package.json # packages/sdk-provider-ethereum/package.json # packages/sdk-provider-solana/package.json # packages/sdk-provider-sui/package.json # packages/sdk-provider-tron/package.json # packages/sdk/package.json # pnpm-lock.yaml
chybisov
added a commit
to lifinance/bigmi
that referenced
this pull request
Jul 13, 2026
Mirrors lifinance/sdk#428. The org's minimumReleaseAge supply-chain gate blocks the <24h-old @yuku / rolldown-plugin-dts@0.27.8 / tsdown@0.22.7 transitive deps pulled in by the TS7 toolchain. pnpm auto-generates this exclude block on install; keep it committed (it was wrongly reverted as an artifact) so 'pnpm install --frozen-lockfile' passes on CI and locally.
chybisov
added a commit
to lifinance/bigmi
that referenced
this pull request
Jul 13, 2026
…es, bump actions) (#63) * ci: fix pnpm 11.12 setup, bump pinned actions, run Verify on PRs The release pipeline broke after pnpm was bumped to 11.12.0: pnpm/action-setup's npm-based self-installer crashes installing that version ("Cannot use 'in' operator to search for 'integrity' in undefined"). - pnpm/action-setup 6.0.8 -> 6.0.9 + standalone: true (fetch the prebuilt binary, bypassing the failing self-installer) -- the actual fix - bump remaining pinned actions to latest: actions/checkout 6.0.2 -> 7.0.0, changesets/action 1.8.0 -> 1.9.0, linear/linear-release-action 0.14.0 -> 0.14.5 (actions/setup-node already at 6.4.0) - run the Verify job on pull_request (opened/synchronize/reopened) so toolchain/CI changes are validated pre-merge; guard Version/Publish to push/dispatch only so a passing PR Verify never triggers a release pnpm stays at 11.12.0 (no revert). * ci: drop standalone from pnpm/action-setup Test whether v6.0.9's newer bootstrap (11.7.0) installs pnpm 11.12.0 via the plain path. standalone:true installed 11.12.0 fine but collided with the runner's pre-existing PNPM_HOME (v10 layout), breaking @pnpm/exe exec. * chore: pin pnpm to 11.10.0 pnpm 11.12.0 breaks pnpm/action-setup's self-installer ('Cannot use in operator ... integrity'). 11.10.0 is structurally identical to the proven-good 11.9.0 (no optionalDependencies) and installs via action-setup. * ci: restore minimumReleaseAgeExclude for fresh toolchain deps Mirrors lifinance/sdk#428. The org's minimumReleaseAge supply-chain gate blocks the <24h-old @yuku / rolldown-plugin-dts@0.27.8 / tsdown@0.22.7 transitive deps pulled in by the TS7 toolchain. pnpm auto-generates this exclude block on install; keep it committed (it was wrongly reverted as an artifact) so 'pnpm install --frozen-lockfile' passes on CI and locally.
chybisov
added a commit
that referenced
this pull request
Jul 15, 2026
Resolve pnpm-lock.yaml conflict by regenerating from merged package.json files (base: main's lockfile + Stellar provider deps). Align sdk-provider-stellar with main's TypeScript 7 migration (#428): bump typescript devDep ^6.0.3 -> ^7.0.2. Verified: check:types, unit tests, and build pass under tsc 7.0.2; pnpm install --frozen-lockfile is consistent.
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
1 participant
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
Migrates the toolchain to TypeScript 7 (
7.0.2, npmlatest) — the native Go compiler.typescript^6.0.3→^7.0.2in the root + all packagestsdown^0.22.3→^0.22.7(root + tron) — its0.22.7peer range adds^7; pullsrolldown-plugin-dts0.27.8(also TS7-aware)pnpm-lock.yaml+pnpm-workspace.yaml— pnpm auto-addedminimumReleaseAgesupply-chain exclusions (exact-version pins) for the new toolchain packages, deliberately fast-tracking these reviewed versions past the age gatetypescript@7ships only the nativetscbinary (the JS compiler API is gone), but nothing on our path needs it:check:typesistsc --noEmit(drop-in), andtsdown+ oxc handle bundling and isolated-declaration.d.tsgeneration. devDependencies only — no runtimedependencieschanged.Verification (full CI sequence, native compiler)
pnpm check(biome)pnpm build(tsdown/oxc)pnpm check:types(tsc --noEmit)pnpm testpnpm check:circular-deps(madge)pnpm install --frozen-lockfileIntegration impact — none
Built the identical source on TS6 vs TS7 and diffed
dist/:.d.tsfiles, 0 differ after normalizing whitespace/comment formatting (the only deltas arerolldown-plugin-dts0.27 cosmetics). Partners on any TS version are unaffected and do not need TS7 themselves..jsfiles differ only by the newer oxc transpiler hoisting anawait/subexpression into a namedconst— semantically identical; no files added/removed.devDependencies, sotypescript/tsdownnever appear in the published artifact.Release
Tooling-only chore — no publishable surface, so no changeset and no version bump (not a minor: there is no new functionality to ship).