chore: support TypeScript 7 and update compatibility docs. - #122
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #122 +/- ##
==========================================
- Coverage 93.57% 93.30% -0.27%
==========================================
Files 4 4
Lines 2209 2240 +31
==========================================
+ Hits 2067 2090 +23
- Misses 142 150 +8 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull request overview
Updates the project to target TypeScript 7 in development tooling, refreshes documented TypeScript compatibility requirements, and adjusts CI/publish workflows accordingly.
Changes:
- Document TypeScript support range in
README.mdand keep peer range at>=5.5.0 <8. - Bump package version and dev tooling versions (notably
typescriptto^7.0.2,tsxto^4.23.0). - Update GitHub Actions workflows (Node patch versions,
actions/checkout), and remove the dedicated TypeScript v7 compatibility workflow.
Reviewed changes
Copilot reviewed 5 out of 6 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| README.md | Adds explicit TypeScript version requirement to the “Requirements” section. |
| package.json | Bumps package version; updates TS/TSX dev deps; removes typescript-rc peer alias while keeping typescript-next. |
| package-lock.json | Locks updated package/devDependency versions consistent with package.json. |
| .github/workflows/typescript-v7.yml | Removes the standalone TypeScript v7/RC compatibility workflow. |
| .github/workflows/publish.yml | Updates checkout action and Node patch version used for publishing. |
| .github/workflows/ci.yml | Updates Node patch versions and checkout action used in CI. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 6 out of 7 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (2)
.github/workflows/typescript-next.yml:27
- After switching to
typescript@next, the workflow no longer prints the resolved TypeScript version. This makes compatibility failures harder to diagnose from CI logs; consider restoring the version output (as the previous RC workflow did).
.github/workflows/typescript-next.yml:37 - This advisory job is intended to validate TypeScript-next compatibility, but it no longer runs the project's
buildscript (the prior workflow did). Without a build step, CI may miss breakages that only surface when Duel runs end-to-end.
No description provided.