Skip to content

fix: align TypeScript 6 lockfile with config#69

Merged
IISweetHeartII merged 1 commit intodevelopfrom
fix/68-lockfile-sync
Apr 21, 2026
Merged

fix: align TypeScript 6 lockfile with config#69
IISweetHeartII merged 1 commit intodevelopfrom
fix/68-lockfile-sync

Conversation

@IISweetHeartII
Copy link
Copy Markdown
Contributor

Summary

  • pin the workspace TypeScript dependency to 6.0.3 so the lockfile and config agree
  • keep the tsconfig updates needed for TS6 compatibility
  • restore frozen-lockfile CI for the TS6 upgrade path

Validation

  • pnpm install --frozen-lockfile
  • pnpm lint
  • pnpm type-check
  • pnpm build
  • pnpm test

Supersedes #68 and helps unblock #66.

@IISweetHeartII
Copy link
Copy Markdown
Contributor Author

#68 CI failure(lockfile/config 불일치)에 대한 후속 PR 리뷰.\n\n### 변경 내용\n1. tsconfig.json: types: ["node"] + ignoreDeprecations: "6.0" 추가 → agentgram-mcp#36과 동일 패턴\n2. package.json: TypeScript를 ^5.9.3에서 6.0.3(exact pin)으로 변경\n3. pnpm-lock.yaml: lockfile refresh로 5.9.3 → 6.0.3 전면 교체\n\n### 판정: APPROVE ✅\n\nCI가 Node 20/22 모두 green이고, mergeStateStatus: CLEAN이야. #68의 blocker였던 lockfile/config 불일치가 exact pin으로 해결됐고, tsconfig.json의 Node globals typing도 올바르게 추가됐어.\n\n한 가지 노트: typescript6.0.3으로 exact pin했는데, agentgram-mcp#36^6.0.3(caret range)를 사용했어. 두 레포 사이에 이런 차이가 있긴 하지만, ax-score 쪽이 더 보수적이고 안전한 선택이야. 나중에 통일하고 싶으면 그때 맞추면 됨.\n\n#66 TypeScript 6 업그레이드 경로 unblock 가능.\n\n---\n🐱 Navi code review

@IISweetHeartII IISweetHeartII merged commit 8d7acc1 into develop Apr 21, 2026
3 checks passed
@IISweetHeartII IISweetHeartII deleted the fix/68-lockfile-sync branch April 21, 2026 01:16
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