-
Notifications
You must be signed in to change notification settings - Fork 4
chore(deps): update devdependencies #81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
📝 WalkthroughWalkthroughBumped several dependency versions in package.json: Pre-merge checks✅ Passed checks (3 passed)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: ASSERTIVE Plan: Pro Disabled knowledge base sources:
⛔ Files ignored due to path filters (2)
📒 Files selected for processing (2)
🔇 Additional comments (4)
Comment |
afb79d0 to
72962ea
Compare
72962ea to
83c7bc4
Compare
|
83c7bc4 to
d32c202
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
⛔ Files ignored due to path filters (1)
src/test/vscode-notebook-perf/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (2)
package.json(2 hunks)src/test/vscode-notebook-perf/package.json(1 hunks)
🧰 Additional context used
🪛 GitHub Actions: CI
src/test/vscode-notebook-perf/package.json
[error] 1-1: npm ci failed: lockfile is out of sync and contains conflicting package versions. Several entries do not satisfy lockfile (e.g., @vscode/test-cli, @vscode/test-web, lint-staged, c8, chokidar, mocha, supports-color, @koa/router, playwright, debug, path-to-regexp, playwright-core, v8-to-istanbul, nano-spawn). Run 'npm install' to regenerate the lockfile and ensure synchronization before re-running 'npm ci'.
package.json
[error] 1-1: npm ci failed: lockfile is out of sync and contains conflicting package versions. Several entries do not satisfy lockfile (e.g., @vscode/test-cli, @vscode/test-web, lint-staged, c8, chokidar, mocha, supports-color, @koa/router, playwright, debug, path-to-regexp, playwright-core, v8-to-istanbul, nano-spawn). Run 'npm install' to regenerate the lockfile and ensure synchronization before re-running 'npm ci'.
🔇 Additional comments (2)
package.json (2)
2286-2288: @VScode test tooling bumps are reasonable.Minor version updates for @vscode/test-cli (0.0.8 → 0.0.12) and @vscode/test-web (0.0.71 → 0.0.74) are low-risk. Ensure test suite continues to pass post-update.
2337-2337: Lint-staged patch bump is safe.Minor patch update (16.2.3 → 16.2.4) for lint-staged carries negligible risk.
d32c202 to
196256c
Compare
39042b9 to
4f7069f
Compare
437310c to
cb40cd1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (2)
package-lock.jsonis excluded by!**/package-lock.jsonsrc/test/vscode-notebook-perf/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (2)
package.json(3 hunks)src/test/vscode-notebook-perf/package.json(1 hunks)
🔇 Additional comments (3)
package.json (2)
2628-2628: Routine devDependency updates approved.cspell 9.2.1 → 9.3.2 and lint-staged 16.2.3 → 16.2.7 are safe patch/minor updates. lint-staged is correctly placed in devDependencies only (production tool, non-runtime).
Also applies to: 2664-2664
2633-2633: Esbuild 0.27.0 contains backwards-incompatible changes—manual verification required.Version 0.27.0 deliberately contains backwards-incompatible changes. Between the previous 0.25.1 and 0.27.0, there are several behavioral changes including:
- Binary loader now uses Uint8Array.fromBase64, which may require specifying target when using this feature with Node unless running Node v25+
- Operating system requirements were raised (Linux kernel 3.2+)
- Multiple source map and build-related fixes that could affect output
The sandbox build command failed due to missing dependencies. Verify locally by running the build scripts (
npm run compile-releaseornpm run compile-tsc+npm run esbuild-release) and confirm output remains valid for your use case.src/test/vscode-notebook-perf/package.json (1)
33-33: Mirrors root @vscode/test-cli update.Matches root package.json bump (^0.0.8 → ^0.0.12). Verification of test suite compilation (above) will cover both locations.
ff08b75 to
17b92f8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (2)
package-lock.jsonis excluded by!**/package-lock.jsonsrc/test/vscode-notebook-perf/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (2)
package.json(3 hunks)src/test/vscode-notebook-perf/package.json(1 hunks)
🔇 Additional comments (2)
package.json (2)
2664-2664: ✓ lint-staged now correctly placed in devDependencies only.Previous review flagged lint-staged appearing in both
dependenciesanddevDependencies. Confirmed it now exists only in devDependencies (line 2664) as a pre-commit tool should be.
2612-2614: Remove this review comment—it does not apply to this repository.This is the deepnote/vscode-deepnote repository, not the Jupyter extension. The current codebase shows no evidence of prior test suite TypeScript compilation errors. The CI workflow (
.github/workflows/ci.yml) includes successful TypeScript type checking, and recent commits show only routine dependency updates with no compilation issues. The VSCode test tooling versions are present inpackage.json, but the stated concern about resolving prior compilation failures has no basis in this repository's history.Likely an incorrect or invalid review comment.
b449346 to
a8ec6f2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
♻️ Duplicate comments (2)
package.json (2)
2634-2636: Test tooling updates blocked by unresolved TypeScript compilation failures.The bumps to
@vscode/test-cli(^0.0.8 → ^0.0.12) and@vscode/test-web(^0.0.71 → ^0.0.76) cannot be verified as working until the TypeScript compilation errors insrc/test/vscode-notebook-perf/are resolved. Confirm that test suite now compiles and runs successfully before merging.
2655-2655: esbuild ^0.27.0 introduces breaking changes; confirm compatibility before merge.v0.27.0 has explicit backwards incompatibilities flagged in earlier reviews:
- Binary loader now prefers
Uint8Array.fromBase64(affects Node.js unless target ≥ node22 or Node ≥ v25)- Raised OS requirements (Linux kernel ≥ 3.2, macOS ≥ 12)
- Maintainers recommend pinning to exact version or patch-only range
Verify that your build target and CI environment requirements remain compatible, and consider changing this to
~0.27.0or a pinned exact version instead of^0.27.0.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (2)
package-lock.jsonis excluded by!**/package-lock.jsonsrc/test/vscode-notebook-perf/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (2)
package.json(3 hunks)src/test/vscode-notebook-perf/package.json(1 hunks)
🔇 Additional comments (1)
package.json (1)
2686-2686: Confirm lint-staged removed from production dependencies.Earlier reviews flagged
lint-stagedappearing in bothdependenciesanddevDependencies. Verify it no longer exists under"dependencies"(lines 2502–2578) and remains only in"devDependencies".
a9b511e to
d38c60e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (2)
package-lock.jsonis excluded by!**/package-lock.jsonsrc/test/vscode-notebook-perf/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (2)
package.json(3 hunks)src/test/vscode-notebook-perf/package.json(1 hunks)
🔇 Additional comments (4)
src/test/vscode-notebook-perf/package.json (1)
33-33: Verify test suite compiles and runs after VSCode test tooling update.Previous reviews flagged TypeScript compilation errors in this test subfolder (missing Node.js types: Buffer, setTimeout, NodeJS namespace, atob). Confirm the test suite now compiles cleanly and passes. Verify
src/test/vscode-notebook-perf/tsconfig.jsonincludes sufficientlibconfiguration (e.g.,"lib": ["ES2022", "DOM"]).package.json (3)
2635-2637: Confirm VSCode test tooling compatibility after bumps.@vscode/test-cli and @vscode/test-web updates are within pre-release ranges. Previous reviews exposed TypeScript compilation failures in the test subfolder after similar updates. Run full test suite (
npm test, integration tests) to confirm no regressions.
2651-2651: Pinned cspell version is acceptable.Patch-level bump (9.2.1 → 9.3.2) with pinned version is low-risk and safe to accept.
2687-2687: lint-staged placement is correct.Confirmed in devDependencies only (correct location for pre-commit tooling). Patch bump (16.2.3 → 16.2.7) is safe.
d38c60e to
c7f2b9b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (2)
package-lock.jsonis excluded by!**/package-lock.jsonsrc/test/vscode-notebook-perf/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (2)
package.json(3 hunks)src/test/vscode-notebook-perf/package.json(1 hunks)
🔇 Additional comments (2)
package.json (2)
2635-2637: Verify VSCode test tooling compatibility after prior TypeScript failures.These pre-release version bumps (0.0.8→0.0.12, 0.0.71→0.0.76) previously exposed TypeScript compilation errors in
src/test/vscode-notebook-perf/src/extension.ts. Confirm the test suite now compiles without TS2688 errors.
2651-2651: cspell patch version update is acceptable.Version 9.2.1 → 9.3.2 is a minor patch bump with no known breaking changes.
d0d9e86 to
6931b10
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
♻️ Duplicate comments (1)
package.json (1)
2656-2656: Constrain esbuild to patch-only range.The caret range
^0.27.0allows minor version upgrades (0.28.0, 0.29.0, etc.). Previous review flagged that esbuild v0.27.0 introduced breaking changes and recommended locking to patch releases. Change to~0.27.0to prevent unexpected breakage.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (2)
package-lock.jsonis excluded by!**/package-lock.jsonsrc/test/vscode-notebook-perf/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (2)
package.json(3 hunks)src/test/vscode-notebook-perf/package.json(1 hunks)
🔇 Additional comments (2)
src/test/vscode-notebook-perf/package.json (1)
33-33: No new concerns. Prior review verified this minor version bump is compatible with the test subfolder's TypeScript configuration.package.json (1)
2651-2651: Correct cspell version bump classification: minor, not patch.
- cspell: 9.2.1 → 9.4.0 (dev-only, minor version bump)
- lint-staged: 16.2.3 → 16.2.7 (dev-only pre-commit tool, patch bump)
While both are development-only tools with acceptable updates, the cspell minor version bump should be reviewed more carefully than a patch bump would warrant. Verify that the minor version upgrade does not introduce breaking changes or significant behavior shifts.
lint-staged placement is correct: it appears only in
devDependencies, not in productiondependencies.
| "@typescript-eslint/parser": "^6.9.0", | ||
| "@vscode/dts": "^0.4.0", | ||
| "@vscode/test-cli": "^0.0.8", | ||
| "@vscode/test-cli": "^0.0.12", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# First, check if the test directory structure exists
ls -la src/test/vscode-notebook-perf/ 2>/dev/null || echo "Directory not found"Repository: deepnote/vscode-deepnote
Length of output: 813
🏁 Script executed:
#!/bin/bash
# Check package.json for test scripts and the specific dependency
cat package.json | grep -A 5 -B 5 "@vscode/test-cli"Repository: deepnote/vscode-deepnote
Length of output: 513
🏁 Script executed:
#!/bin/bash
# Check if the extension.ts file exists and inspect it for type issues
if [ -f "src/test/vscode-notebook-perf/src/extension.ts" ]; then
echo "=== File exists, checking for type imports ==="
head -30 src/test/vscode-notebook-perf/src/extension.ts
else
echo "File not found at expected path"
# Try to find it
find . -name "extension.ts" -type f 2>/dev/null | head -10
fiRepository: deepnote/vscode-deepnote
Length of output: 839
🏁 Script executed:
#!/bin/bash
# Check the structure of the test directory
find src/test/vscode-notebook-perf -type f -name "*.ts" -o -name "*.json" | head -20Repository: deepnote/vscode-deepnote
Length of output: 495
🏁 Script executed:
#!/bin/bash
# Check the test directory's tsconfig.json
cat src/test/vscode-notebook-perf/tsconfig.jsonRepository: deepnote/vscode-deepnote
Length of output: 982
🏁 Script executed:
#!/bin/bash
# Check the test directory's package.json
cat src/test/vscode-notebook-perf/package.jsonRepository: deepnote/vscode-deepnote
Length of output: 1352
🏁 Script executed:
#!/bin/bash
# Check if there are any Node type references in extension.ts
grep -n "Node\|DOM" src/test/vscode-notebook-perf/src/extension.ts || echo "No Node/DOM references found in extension.ts"Repository: deepnote/vscode-deepnote
Length of output: 107
🏁 Script executed:
#!/bin/bash
# Search for any type definition issues or Node imports in the test directory
rg "import.*from.*node" src/test/vscode-notebook-perf/ || echo "No node imports found"Repository: deepnote/vscode-deepnote
Length of output: 89
🏁 Script executed:
#!/bin/bash
# Check if runTest.js exists and inspect it
if [ -f "src/test/vscode-notebook-perf/out/test/runTest.js" ]; then
echo "=== runTest.js exists ==="
cat src/test/vscode-notebook-perf/out/test/runTest.js
else
echo "runTest.js not found in out/ directory"
find src/test/vscode-notebook-perf -name "runTest.js" -o -name "runTest.ts" 2>/dev/null
fiRepository: deepnote/vscode-deepnote
Length of output: 106
🏁 Script executed:
#!/bin/bash
# Check for test files in the test directory
find src/test/vscode-notebook-perf/src -name "*.ts" -type fRepository: deepnote/vscode-deepnote
Length of output: 155
🏁 Script executed:
#!/bin/bash
# Try to compile the test extension to verify if there are actual TypeScript errors
cd src/test/vscode-notebook-perf
npm run compile 2>&1 | head -50Repository: deepnote/vscode-deepnote
Length of output: 139
🏁 Script executed:
#!/bin/bash
# Install dependencies for the test extension
cd src/test/vscode-notebook-perf
npm install 2>&1 | tail -20Repository: deepnote/vscode-deepnote
Length of output: 211
🏁 Script executed:
#!/bin/bash
# After install, try to compile
cd src/test/vscode-notebook-perf
npm run compile 2>&1Repository: deepnote/vscode-deepnote
Length of output: 141
Fix TypeScript configuration to include Node type definitions.
The test extension uses NodeJS.Timeout (line 55 of src/test/vscode-notebook-perf/src/extension.ts) but the tsconfig.json only includes "ES2022" in the lib array. Add "DOM" and "Node" to the lib array in src/test/vscode-notebook-perf/tsconfig.json to resolve Node type definitions, even though @types/node is already in devDependencies.
🤖 Prompt for AI Agents
In src/test/vscode-notebook-perf/tsconfig.json (referenced from package.json
around line 2635), the TypeScript libs only include "ES2022" which leaves out
Node types used by the extension; edit that tsconfig.json to add "DOM" and
"Node" to the "lib" array (e.g., ["ES2022","DOM","Node"]) so NodeJS.Timeout and
other DOM/Node ambient types are available at compile time.
8fc22c4 to
b1d6168
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
♻️ Duplicate comments (1)
package.json (1)
2656-2656: Constrain esbuild to patch-only range.esbuild v0.27.0 has backwards-incompatible changes (Uint8Array.fromBase64 requires Node ≥25.0.0, Go toolchain ≥3.2 Linux/≥12 macOS). Caret range
^0.27.0permits minor version upgrades that may introduce new breaking changes. Change to~0.27.0or0.27.0to lock updates to patch releases.- "esbuild": "^0.27.0", + "esbuild": "~0.27.0",
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (2)
package-lock.jsonis excluded by!**/package-lock.jsonsrc/test/vscode-notebook-perf/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (2)
package.json(3 hunks)src/test/vscode-notebook-perf/package.json(1 hunks)
🔇 Additional comments (3)
src/test/vscode-notebook-perf/package.json (1)
33-33: @vscode/test-cli minor version bump is acceptable.Aligns with root package.json update and prior resolution (commit a9b511e). Correctness depends on TypeScript configuration fix in
tsconfig.json(add"DOM"and"Node"tolibarray if not already present).package.json (2)
2651-2651: cspell pinned to exact version; safe.
2687-2687: lint-staged moved to devDependencies only; issue resolved.Previously flagged as appearing in both dependencies and devDependencies. Current code shows only devDependencies placement, which is correct for a pre-commit tool.
package.json
Outdated
| "@vscode/test-cli": "^0.0.12", | ||
| "@vscode/test-electron": "^2.3.9", | ||
| "@vscode/test-web": "^0.0.71", | ||
| "@vscode/test-web": "^0.0.76", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
find . -path "*/src/test/vscode-notebook-perf/tsconfig.json" -type fRepository: deepnote/vscode-deepnote
Length of output: 113
🏁 Script executed:
cat ./src/test/vscode-notebook-perf/tsconfig.jsonRepository: deepnote/vscode-deepnote
Length of output: 982
@vscode/test-cli and @vscode/test-web pre-release bumps require TypeScript config fix: add "DOM" and "Node" to lib array in src/test/vscode-notebook-perf/tsconfig.json.
The @vscode/test-cli (^0.0.8 → ^0.0.12) and @vscode/test-web (^0.0.71 → ^0.0.76) updates are incremental pre-release versions. However, src/test/vscode-notebook-perf/tsconfig.json currently only includes "ES2022" in its lib array and is missing "DOM" and "Node" types. Update the lib array from ["ES2022"] to ["ES2022", "DOM", "Node"] to resolve TypeScript errors in the test folder.
🤖 Prompt for AI Agents
In src/test/vscode-notebook-perf/tsconfig.json around the project's test config
(update referenced because package.json lines 2635–2637 indicate test deps
changed), the tsconfig's "lib" array currently only contains "ES2022";
TypeScript needs DOM and Node types for the updated @vscode/test-cli and
@vscode/test-web versions, so modify the "lib" array to include "DOM" and "Node"
(i.e., change ["ES2022"] to ["ES2022", "DOM", "Node"]) and save to eliminate the
type errors in that test folder.
d93faaa to
134151f
Compare
134151f to
8b9dd0b
Compare
This PR contains the following updates:
4.1.14->4.1.176.9.0->6.21.06.9.0->6.21.06.9.0->6.21.00.4.0->0.4.1^0.0.8->^0.0.122.3.9->2.5.2^0.0.71->^0.0.778.9.0->8.15.010.4.21->10.4.222.8.1->2.8.24.0.6->4.0.94.3.10->4.5.07.1.1->7.1.22.1.0->2.1.19.2.1->9.4.01.22.3->1.24.00.10.63->0.10.64^0.25.1->^0.27.01.3.19->1.3.338.52.0->8.57.19.0.0->9.1.22.29.0->2.32.046.8.2->46.10.16.7.1->6.10.23.1.0->3.3.05.0.1->5.5.47.33.2->7.37.54.6.0->4.6.25.0.0->5.0.12.0.0->2.1.01.4.1->1.5.04.2.2->4.4.216.2.3->16.2.710.2.0->10.4.311.0.1->11.7.52.2.0->2.2.13.0.0->3.7.45.0.1->5.0.101.15.2->1.15.30.7.4->0.7.64.1.14->4.1.171.3.8->1.3.194.19.4->4.21.05.4.5->5.9.35.8.3->5.9.31.3.1->1.4.15.0.9->5.0.10Release Notes
tailwindlabs/tailwindcss (@tailwindcss/postcss)
v4.1.17Compare Source
Fixed
@variantinside legacy JS APIs (#19263)v4.1.16Compare Source
Fixed
&(#19184)& > :pseudoand& :pseudoarbitrary variants (#19178)v4.1.15Compare Source
Fixed
color-mixfallback (#19069):deep,:slotted, and:global(#19094)not-*,has-*, andin-*(#19100)theme(…)function (#19111)\tis used in at-rules (#19130)0values (#19095)break-wordstowrap-break-word(#19157)Changed
postinstallscript from oxide ([#19149])(#19149)typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v6.21.0Compare Source
🚀 Features
export plugin metadata
allow
parserOptions.project: falseeslint-plugin: add rule prefer-find
🩹 Fixes
eslint-plugin: [no-unused-vars] don't report on types referenced in export assignment expression
eslint-plugin: [switch-exhaustiveness-check] better support for intersections, infinite types, non-union values
eslint-plugin: [consistent-type-imports] dont report on types used in export assignment expressions
eslint-plugin: [no-unnecessary-condition] handle left-hand optional with exactOptionalPropertyTypes option
eslint-plugin: [class-literal-property-style] allow getter when same key setter exists
eslint-plugin: [no-unnecessary-type-assertion] provide valid fixes for assertions with extra tokens before
askeyword❤️ Thank You
You can read about our versioning strategy and releases on our website.
v6.20.0Compare Source
🚀 Features
🩹 Fixes
eslint-plugin: [no-useless-template-literals] incorrect bigint autofix result
eslint-plugin: [prefer-nullish-coalescing] treat any/unknown as non-nullable
eslint-plugin: [no-useless-template-literals] report Infinity & NaN
eslint-plugin: [prefer-readonly] disable checking accessors
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v6.19.1Compare Source
🩹 Fixes
type-utils: preventing isUnsafeAssignment infinite recursive calls
eslint-plugin: [no-unnecessary-condition] fix false positive for type variable
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v6.19.0Compare Source
🚀 Features
eslint-plugin: [prefer-promise-reject-errors] add rule
eslint-plugin: [no-array-delete] add new rule
eslint-plugin: [no-useless-template-literals] add fix suggestions
🩹 Fixes
eslint-plugin: [no-unnecessary-type-assertion] detect unnecessary non-null-assertion on a call expression
eslint-plugin: [no-unnecesary-type-assertion] treat unknown/any as nullable
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v6.18.1Compare Source
🩹 Fixes
eslint-plugin: [no-non-null-assertion] provide valid fix when member access is on next line
eslint-plugin: [no-unnecessary-condition] improve checking optional callee
eslint-plugin: [prefer-readonly] support modifiers of unions and intersections
eslint-plugin: [switch-exhaustiveness-check] fix new allowDefaultCaseForExhaustiveSwitch option
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v6.18.0Compare Source
🚀 Features
typescript-estree: throw on invalid update expressions
eslint-plugin: [no-var-requires, no-require-imports] allow option
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v6.17.0Compare Source
Bug Fixes
patternsorpathsin options are empty (#8108) (675e987)Features
defaultcase on an already exhaustiveswitch(#7539) (6a219bd)You can read about our versioning strategy and releases on our website.
v6.16.0Compare Source
Bug Fixes
Features
You can read about our versioning strategy and releases on our website.
v6.15.0Compare Source
Features
You can read about our versioning strategy and releases on our website.
v6.14.0Compare Source
Bug Fixes
no-unsafe-unary-minus(#7998) (705370a)Features
You can read about our versioning strategy and releases on our website.
6.13.2 (2023-12-04)
Note: Version bump only for package @typescript-eslint/eslint-plugin
You can read about our versioning strategy and releases on our website.
6.13.1 (2023-11-28)
Note: Version bump only for package @typescript-eslint/eslint-plugin
You can read about our versioning strategy and releases on our website.
v6.13.2Compare Source
Note: Version bump only for package @typescript-eslint/eslint-plugin
You can read about our versioning strategy and releases on our website.
v6.13.1Compare Source
Note: Version bump only for package @typescript-eslint/eslint-plugin
You can read about our versioning strategy and releases on our website.
v6.13.0Compare Source
Note: Version bump only for package @typescript-eslint/eslint-plugin
You can read about our versioning strategy and releases on our website.
v6.12.0Compare Source
Bug Fixes
ignoreClassesThatImplementAnInterfaceis set (#7705) (155aa1f)Features
You can read about our versioning strategy and releases on our website.
v6.11.0Compare Source
Bug Fixes
allowTypedFunctionExpressions(#7553) (be2777c)Features
no-unsafe-unary-minusrule (#7390) (c4709c2)CodePathselector types (#7551) (99a026f)You can read about our versioning strategy and releases on our website.
v6.10.0Compare Source
Bug Fixes
Features
You can read about our versioning strategy and releases on our website.
6.9.1 (2023-10-30)
Bug Fixes
You can read about our versioning strategy and releases on our website.
v6.9.1Compare Source
Bug Fixes
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin-tslint)
v6.21.0Compare Source
🚀 Features
parserOptions.project: false(#8339)🩹 Fixes
JSXElementtype to theJSXAttribute['value'](#8285)askeyword (#8326)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v6.20.0Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v6.19.1Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v6.19.0Compare Source
🚀 Features
🩹 Fixes
usingas the variable keyword forfor..inloops (#7649)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v6.18.1Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v6.18.0Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v6.17.0Compare Source
Bug Fixes
patternsorpathsin options are empty (#8108) (675e987)Features
defaultcase on an already exhaustiveswitch(#7539) (6a219bd)You can read about our versioning strategy and releases on our website.
v6.16.0Compare Source
Bug Fixes
Features
Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.