Skip to content
This repository was archived by the owner on May 12, 2026. It is now read-only.

chore(release): bump version to 7.1.0#284

Merged
JegernOUTT merged 7 commits into
mainfrom
dev
May 4, 2026
Merged

chore(release): bump version to 7.1.0#284
JegernOUTT merged 7 commits into
mainfrom
dev

Conversation

@JegernOUTT
Copy link
Copy Markdown
Member

Update version across all components:

  • IntelliJ plugin (gradle.properties)
  • refact-chat-js (package.json, package-lock.json)
  • VSCode extension (package.json + dependency)
  • refact-lsp engine (Cargo.toml)

Add update-dependencies.sh script for IntelliJ plugin to automate GUI build and LSP binary bundling.

Update version across all components:
- IntelliJ plugin (gradle.properties)
- refact-chat-js (package.json, package-lock.json)
- VSCode extension (package.json + dependency)
- refact-lsp engine (Cargo.toml)

Add update-dependencies.sh script for IntelliJ plugin to automate GUI
build and LSP binary bundling.
Move unix::fs::PermissionsExt import inside #[cfg(unix)] block and add
no-op #[cfg(windows)] implementation since Windows doesn't require
explicit execute permissions.

Also add skipLibCheck to VSCode tsconfig for build compatibility.
….0.6+ syntax

mermaid@11.x (dep of refact-chat-js) lists @types/d3 as a production
dependency, which pulls in @types/d3-dispatch@3.0.6+ that uses const
type parameters (TypeScript 5.0 syntax). TypeScript 4.x cannot parse
this at all, skipLibCheck does not help since it is a parser error.
@JegernOUTT
Copy link
Copy Markdown
Member Author

Root cause analysis

The CI failure was not fixed by skipLibCheck: true alone (commit 41649a4) because the issue is a parser error, not a type-checking error.

Dependency chain

refact-chat-js → mermaid@11.x → @types/d3@^7.4.3 → @types/d3-dispatch@3.0.6+

mermaid@11.x incorrectly lists @types/d3 as a production dependency (not devDependency), which causes the VSCode extension to install @types/d3-dispatch@3.0.6+ as a transitive dep.

Why skipLibCheck didn't help

@types/d3-dispatch@3.0.6 uses const type parameters (introduced in TypeScript 5.0). TypeScript 4.x cannot even parse this syntax — it fails with:

TS1139: Type parameter declaration expected

skipLibCheck only skips type-checking of .d.ts files; parsing still happens and fails with TS 4.x.

Fix (commit 2ce0637)

Upgraded TypeScript from ^4.7.4^5.0.0 in devDependencies. TypeScript 5.x can parse the new const type parameter syntax.

@JegernOUTT JegernOUTT merged commit 7baf248 into main May 4, 2026
19 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant