chore(deps): upgrade TypeScript to 6.0 and ts-jest to 29.4.11

[frbrkoala]

Bump typescript ~5.9.3 -> ~6.0.3. ts-jest 29.4.6 caps its typescript peer at "<6", so also bump ts-jest to ^29.4.11 (peer ">=4.3 <7"); ts-node 10.9.2 already supports TS 6.

TS 6 reports moduleResolution "node" (node10) as deprecated (removed in TS 7). Add "ignoreDeprecations": "6.0" to tsconfig.json as the sanctioned bridge until moduleResolution is modernized (e.g. to node16/bundler) before TS 7.

Verified: tsc build, jest (473 tests across 22 suites), and cdk synth all pass.

What does this PR do?

🛑 Please open an issue first to discuss any significant work and flesh out details/direction — we would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.

Motivation

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• New blueprint (adding a new protocol — see checklist below)
• Documentation update
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Testing

• I have run npm run build successfully
• I have run npm run test and all tests pass
• I have run npx cdk synth with a sample .env (e.g. from blueprints/dummy/samples/) and it succeeds
• I have run pre-commit hooks: npm run run-pre-commit

New Blueprint Checklist (if adding a protocol)

• Blueprint follows the structure of blueprints/dummy/ (reference implementation)
• Blueprint README follows the standard template (matches Dummy section titles and ordering)
• Setup section points to Getting Started (not inline instructions)
• Deployment section leads with AI-driven deployment (Option 1) and manual as Option 2
• Sample .env files are provided for at least one network (mainnet or testnet)
• Configuration scripts follow the install/run dispatch pattern (see blueprints/dummy/)
• Blueprint page added to website/docs/blueprints/ (.mdx mirror importing README)
• Client Release Channels table added to README under Additional Resources

Documentation

• I have updated relevant documentation (if applicable)
• I have run cd website && npm run build with no broken links (if docs changed)

License

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details
npm/semver	7.8.5	🟢 6.6	Details Check Score Reason Maintained 🟢 10 18 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Packaging ⚠️ -1 packaging workflow not detected Security-Policy 🟢 10 security policy file detected Code-Review 🟢 8 Found 14/17 approved changesets -- score normalized to 8 Binary-Artifacts 🟢 10 no binaries found in the repo CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Pinned-Dependencies ⚠️ 0 dependency not pinned by hash detected -- score normalized to 0 Fuzzing ⚠️ 0 project is not fuzzed License 🟢 10 license file detected Signed-Releases ⚠️ -1 no releases found Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md SAST 🟢 9 SAST tool detected but not run on all commits
npm/ts-jest	29.4.11	🟢 4.8	Details Check Score Reason Maintained 🟢 10 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10 Code-Review ⚠️ -1 Found no human activity in the last 30 changesets Dangerous-Workflow ⚠️ 0 dangerous workflow patterns detected Packaging ⚠️ -1 packaging workflow not detected CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Binary-Artifacts 🟢 10 no binaries found in the repo Pinned-Dependencies 🟢 10 all dependencies are pinned Security-Policy ⚠️ 0 security policy file not detected License 🟢 10 license file detected Fuzzing ⚠️ 0 project is not fuzzed Signed-Releases ⚠️ -1 no releases found Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md SAST 🟢 10 SAST tool is run on all commits
npm/typescript	6.0.3	🟢 7.9	Details Check Score Reason Code-Review 🟢 10 all changesets reviewed Maintained 🟢 10 21 commit(s) and 16 issue activity found in the last 90 days -- score normalized to 10 Dependency-Update-Tool 🟢 10 update tool detected Packaging ⚠️ -1 packaging workflow not detected Security-Policy 🟢 10 security policy file detected Token-Permissions 🟢 9 detected GitHub workflow tokens with excessive permissions Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Signed-Releases ⚠️ 0 Project has not signed or included provenance with any releases. Vulnerabilities ⚠️ 1 9 existing vulnerabilities detected Branch-Protection ⚠️ -1 internal error: error during GetBranch(release-5.9): error during branchesHandler.query: internal error: githubv4.Query: Resource not accessible by integration License 🟢 10 license file detected Binary-Artifacts 🟢 10 no binaries found in the repo Pinned-Dependencies 🟢 7 dependency not pinned by hash detected -- score normalized to 7 SAST 🟢 10 SAST tool is run on all commits Fuzzing 🟢 10 project is fuzzed CI-Tests 🟢 10 30 out of 30 merged PRs checked by a CI test -- score normalized to 10 Contributors 🟢 10 project has 38 contributing companies or organizations

Scanned Files

• package-lock.json

[github-actions]

Scan for commit: 304a1b0 | Updated: 2026-07-06 04:09:30 UTC

🔒 Security Scan Results

Scanned files: 3

⚠️ Security findings detected. Please review and address before merging.