chore(deps): update all dependency updates (major) - #396
Conversation
📝 WalkthroughWalkthroughThis PR updates GitHub Actions versions and bumps four development dependencies: jsdom, lint-staged, TypeScript, and vite-plugin-dts. No application logic or exported entities change. ChangesVersion and Dependency Bumps
Estimated code review effort: 1 (Trivial) | ~3 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
.github/workflows/ci.yml (1)
15-15: 🔒 Security & Privacy | 🔵 Trivial | ⚡ Quick winVersion bump looks correct; consider
persist-credentials: false.
actions/checkout@v7is valid. Static analysis flags that credentials aren't set to non-persistent, which is a pre-existing config gap (unrelated to this version bump) but worth addressing while touching this line, since checkout persists the token to the git config by default.🔒 Optional hardening
- uses: actions/checkout@v7 + with: + persist-credentials: false🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/ci.yml at line 15, The checkout version bump is fine, but the `actions/checkout` step still leaves persisted credentials by default. Update the existing checkout step to explicitly set `persist-credentials: false` so the token is not written to git config; use the `actions/checkout` step in the CI workflow as the place to make this change.Source: Linters/SAST tools
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Line 41: The package.json engine range is too low for the current lint-staged
dependency, which means Node 20 users can still install successfully but fail
when the pre-commit hook runs. Update the engines field in package.json to match
the Node 24 baseline used by .nvmrc and CI, or alternatively downgrade
lint-staged to a version compatible with Node 20; use the package.json engines
entry and the lint-staged dependency as the main symbols to locate the fix.
---
Nitpick comments:
In @.github/workflows/ci.yml:
- Line 15: The checkout version bump is fine, but the `actions/checkout` step
still leaves persisted credentials by default. Update the existing checkout step
to explicitly set `persist-credentials: false` so the token is not written to
git config; use the `actions/checkout` step in the CI workflow as the place to
make this change.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: f8fba563-8bc9-44ae-b11b-4af3a09898b7
⛔ Files ignored due to path filters (1)
yarn.lockis excluded by!**/yarn.lock,!**/*.lock
📒 Files selected for processing (2)
.github/workflows/ci.ymlpackage.json
🔗 Linked repositories identified
CodeRabbit considers these linked repositories for cross-repo context during reviews:
ftrackhq/ftrack(manual)
| "husky": "^9.1.7", | ||
| "jsdom": "^29.0.0", | ||
| "lint-staged": "^16.2.7", | ||
| "lint-staged": "^17.0.0", |
There was a problem hiding this comment.
🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🌐 Web query:
What is the minimum Node.js version required by lint-staged v17?
💡 Result:
The minimum Node.js version required by lint-staged v17 is Node.js v22.22.1 [1][2][3]. Starting with v17, support for Node.js v20 was removed [1][2].
Citations:
- 1: https://github.com/lint-staged/lint-staged/blob/main/MIGRATION.md
- 2: https://github.com/lint-staged/lint-staged/releases/tag/v17.0.0
- 3: https://github.com/lint-staged/lint-staged/blob/HEAD/CHANGELOG.md
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf '\n== package.json ==\n'
sed -n '1,220p' package.json
printf '\n== Husky/pre-commit hooks ==\n'
for f in .husky/pre-commit .husky/*; do
[ -f "$f" ] && { echo "--- $f"; sed -n '1,120p' "$f"; }
done
printf '\n== CI/workflow Node references ==\n'
rg -n --hidden --glob '.github/workflows/*.yml' --glob '.github/workflows/*.yaml' 'node-version|setup-node|actions/setup-node|node [0-9]|NODE_VERSION|volta|engines' .github/workflows || trueRepository: ftrackhq/ftrack-javascript
Length of output: 2709
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf '\n== .nvmrc ==\n'
sed -n '1,40p' .nvmrc
printf '\n== CI workflow ==\n'
sed -n '1,120p' .github/workflows/ci.ymlRepository: ftrackhq/ftrack-javascript
Length of output: 1395
Raise the Node engine floor or downgrade lint-staged. .nvmrc and CI already use Node 24, but package.json still advertises >=20.0.0; anyone on Node 20 will hit a failing yarn lint-staged pre-commit hook because lint-staged@17 requires Node >=22.22.1.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@package.json` at line 41, The package.json engine range is too low for the
current lint-staged dependency, which means Node 20 users can still install
successfully but fail when the pre-commit hook runs. Update the engines field in
package.json to match the Node 24 baseline used by .nvmrc and CI, or
alternatively downgrade lint-staged to a version compatible with Node 20; use
the package.json engines entry and the lint-staged dependency as the main
symbols to locate the fix.
0e0bc93 to
b21e2e6
Compare
|
There was a problem hiding this comment.
🧹 Nitpick comments (1)
.github/workflows/ci.yml (1)
15-15: 🔒 Security & Privacy | 🔵 Trivial | ⚡ Quick winConsider setting
persist-credentials: false.Static analysis flags this checkout step for not disabling credential persistence, which can leak the
GITHUB_TOKENto subsequent steps unnecessarily.🔒️ Suggested hardening
- - uses: actions/checkout@v7 + - uses: actions/checkout@v7 + with: + persist-credentials: falseAs per static analysis hints, zizmor flagged: "credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false".
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/ci.yml at line 15, The checkout step in the CI workflow should disable credential persistence to avoid exposing the GitHub token to later steps. Update the actions/checkout usage in the workflow to set persist-credentials to false on the checkout action, keeping the change localized to the checkout job configuration.Source: Linters/SAST tools
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In @.github/workflows/ci.yml:
- Line 15: The checkout step in the CI workflow should disable credential
persistence to avoid exposing the GitHub token to later steps. Update the
actions/checkout usage in the workflow to set persist-credentials to false on
the checkout action, keeping the change localized to the checkout job
configuration.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: b9ff590f-87ea-4cb9-b3a3-14da58c65547
📒 Files selected for processing (2)
.github/workflows/ci.ymlpackage.json
🔗 Linked repositories identified
CodeRabbit considers these linked repositories for cross-repo context during reviews:
ftrackhq/ftrack(manual)
✅ Files skipped from review due to trivial changes (1)
- package.json
b21e2e6 to
f394ac4
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/ci.yml:
- Around line 15-17: Update the actions/checkout step to set persist-credentials
to false, ensuring the checkout token is not retained for later
repository-controlled commands; leave the actions/setup-node step unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 268eca08-48ae-47c3-80d5-a65e9f7d33d0
📒 Files selected for processing (2)
.github/workflows/ci.ymlpackage.json
🔗 Linked repositories identified
CodeRabbit considers these linked repositories for cross-repo context during reviews:
ftrackhq/ftrack(manual)
🚧 Files skipped from review as they are similar to previous changes (1)
- package.json
| - uses: actions/checkout@v7 | ||
| - name: Using Node.js from .nvmrc | ||
| uses: actions/setup-node@v6 | ||
| uses: actions/setup-node@v7 |
There was a problem hiding this comment.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
sed -n '1,220p' .github/workflows/ci.ymlRepository: ftrackhq/ftrack-javascript
Length of output: 1359
Disable persisted checkout credentials.
actions/checkout leaves the GitHub token available to later repo-controlled commands by default. Add persist-credentials: false unless this job needs authenticated git access.
Proposed fix
- uses: actions/checkout@v7
+ with:
+ persist-credentials: false📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - uses: actions/checkout@v7 | |
| - name: Using Node.js from .nvmrc | |
| uses: actions/setup-node@v6 | |
| uses: actions/setup-node@v7 | |
| - uses: actions/checkout@v7 | |
| with: | |
| persist-credentials: false | |
| - name: Using Node.js from .nvmrc | |
| uses: actions/setup-node@v7 |
🧰 Tools
🪛 zizmor (1.26.1)
[warning] 15-15: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false
(artipacked)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @.github/workflows/ci.yml around lines 15 - 17, Update the actions/checkout
step to set persist-credentials to false, ensuring the checkout token is not
retained for later repository-controlled commands; leave the actions/setup-node
step unchanged.
Source: Linters/SAST tools
f394ac4 to
0b08ae6
Compare
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Around line 40-41: Regenerate yarn.lock to reflect the updated dependency
ranges for jsdom, lint-staged, typescript, and vite-plugin-dts in package.json.
Use the repository’s Yarn workflow so the lockfile is consistent and immutable
installs succeed.
- Line 40: Update the jsdom dependency version in package.json from the
unavailable ^30.0.0 range to a published compatible release, using ^29.1.1.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: df160347-ad79-4ae8-9dc3-3df2e0cfef8e
📒 Files selected for processing (2)
.github/workflows/ci.ymlpackage.json
🔗 Linked repositories identified
CodeRabbit considers these linked repositories for cross-repo context during reviews:
ftrackhq/ftrack(manual)
| "husky": "^9.1.7", | ||
| "jsdom": "^29.0.0", | ||
| "lint-staged": "^16.2.7", | ||
| "jsdom": "^30.0.0", |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== package.json excerpt =="
nl -ba package.json | sed -n '34,46p'
echo
echo "== yarn.lock jsdom entries =="
rg -n '^jsdom@|jsdom@' yarn.lock | sed -n '1,40p'
echo
echo "== published jsdom metadata (registry) =="
python3 - <<'PY'
import json, urllib.request
url = "https://registry.npmjs.org/jsdom"
with urllib.request.urlopen(url, timeout=20) as r:
data = json.load(r)
print("dist-tags.latest:", data.get("dist-tags", {}).get("latest"))
versions = sorted(data.get("versions", {}).keys(), key=lambda s: [int(x) if x.isdigit() else x for x in __import__('re').split(r'(\d+)', s)])
print("recent versions:", versions[-8:])
PYRepository: ftrackhq/ftrack-javascript
Length of output: 231
🌐 Web query:
jsdom npm latest release 30.0.0 29.1.1
💡 Result:
As of today, July 27, 2026, the latest version of the jsdom package on npm is 29.1.1 [1][2][3]. This version was released on April 30, 2026 [4][5][3]. There is no official release of the jsdom package itself at version 30.0.0 [2][3]. While version 30.0.0 exists for related packages such as jest-environment-jsdom [6], it does not apply to the core jsdom library. Users should continue to track the official jsdom repository on GitHub for future release announcements [2].
Citations:
- 1: https://www.npmjs.com/package/jsdom
- 2: https://github.com/jsdom/jsdom/releases
- 3: https://deps.dev/npm/jsdom/29.1.1/versions
- 4: https://npmx.dev/package/jsdom
- 5: https://github.com/jsdom/jsdom/releases/tag/v29.1.1
- 6: https://npmx.dev/package/jest-environment-jsdom/v/30.0.0
🏁 Script executed (no clone):
#!/bin/bash
set -euo pipefail
python3 - <<'PY'
import json, urllib.request
data = json.load(urllib.request.urlopen("https://registry.npmjs.org/jsdom", timeout=20))
print(data["dist-tags"].get("latest"))
PY
Length of output: 2411
Use a published jsdom release. ^30.0.0 does not resolve on npm; the latest official jsdom release is 29.1.1, so this dependency range will break installs until it’s changed.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@package.json` at line 40, Update the jsdom dependency version in package.json
from the unavailable ^30.0.0 range to a published compatible release, using
^29.1.1.
Source: MCP tools
| "jsdom": "^30.0.0", | ||
| "lint-staged": "^17.0.0", |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== package.json (relevant deps) =="
cat -n package.json | sed -n '1,140p'
echo
echo "== package manager config files =="
fd -a -t f 'package.json|yarn.lock|.yarnrc.yml|.npmrc|pnpm-lock.yaml|package-lock.json' .
echo
echo "== yarn.lock entries for mentioned packages =="
rg -n '^(jsdom|lint-staged|typescript|vite-plugin-dts)@|^ version "|^ resolution:|^ dependencies:|^ (jsdom|lint-staged|typescript|vite-plugin-dts):' yarn.lockRepository: ftrackhq/ftrack-javascript
Length of output: 28880
Regenerate yarn.lock for these dependency bumps. yarn.lock still pins the old ranges for jsdom, lint-staged, typescript, and vite-plugin-dts, so immutable Yarn installs will fail until the lockfile is updated.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@package.json` around lines 40 - 41, Regenerate yarn.lock to reflect the
updated dependency ranges for jsdom, lint-staged, typescript, and
vite-plugin-dts in package.json. Use the repository’s Yarn workflow so the
lockfile is consistent and immutable installs succeed.
Source: MCP tools
This PR contains the following updates:
v5→v6v6→v7v6→v7^29.0.0→^30.0.0^16.2.7→^17.0.0^6.0.0→^7.0.0^4.5.4→^5.0.0Release Notes
actions/cache (actions/cache)
v6.1.0Compare Source
What's Changed
Full Changelog: actions/cache@v6...v6.1.0
v6.0.0Compare Source
What's Changed
Full Changelog: actions/cache@v5...v6.0.0
v6Compare Source
actions/checkout (actions/checkout)
v7.0.1Compare Source
v7.0.0Compare Source
v7Compare Source
actions/setup-node (actions/setup-node)
v7.0.0Compare Source
What's Changed
Enhancements:
Bug fixes:
mirrorTokeningetManifestif it's provided by @deiga in #1548Documentation updates:
Dependency update:
New Contributors
Full Changelog: actions/setup-node@v6...v7.0.0
v7Compare Source
jsdom/jsdom (jsdom)
v30.0.1Compare Source
v30.0.0Compare Source
v29.1.1Compare Source
'border-radius'computed style serialization. (@asamuzaK)'background-origin'and'background-clip'CSS properties. (@asamuzaK)getComputedStyle(), before the cache warms up. (@asamuzaK)v29.1.0Compare Source
getComputedStyle()sometimes returning outdated results after CSS was modified. (@asamuzaK)v29.0.2Compare Source
getComputedStyle(). Computed value rules are now applied across a broader set of properties, and include fixes related to inheritance, defaulting keywords, custom properties, and color-related values such ascurrentcolorand system colors. (@asamuzaK)'background' and'border'shorthand parsing. (@asamuzaK)lint-staged/lint-staged (lint-staged)
v17.2.0Compare Source
Minor Changes
#1823
ee156cc- The chunking of tasks based on maximum command line argument length has been re-implemented to be more precise. Now the chunking happens based on the final generated command string, instead of just the list of staged files like previously. This benefits mainly Windows platforms and function commands like:Where the spawned command is literally
"tsc"without any extra arguments. Previously, this was still chunked when a lot of files were staged. Now, it probably won't be chunked because the length of the command is just three letters.Also, native JavaScript/Node.js function tasks won't be chunked at all, when previously they were run multiple times when chunked:
v17.1.1Compare Source
Patch Changes
a626a9f- It's now possible to set--max-arg-length=Infinityto effectively disable chunking of tasks based on the number of staged files. The parsing and validation of the numeric CLI options--max-arg-lengthand--concurrencyhas been improved.v17.1.0Compare Source
Minor Changes
#1816
7568d4f- The console output of lint-staged has been simplified so that there's less interactive spinners and more explicit messages like "Started…" -> "Done!". The primary purpose of this was to removeListr2, a very large dependency.Before:
Size of
node_modules/after installing:1561.7 kBwith 29 packages.Fancy interactive spinners, but output dynamically changes:
After:
Size of
node_modules/after installing:974.0 kBwith 5 packages (37.6 % smaller, 82.7 % less transitive dependencies).Simpler but more explicit output:
Patch Changes
#1816
c19079d- Try to restore hidden unstaged changes when using--no-revert.#1818
efb23a2- Console output colors are enabled/disabled more consistently.#1818
26112a1- Failed JS function tasks now properly kill other tasks, unless--continue-on-erroris used. Previously their failure didn't affect other tasks.v17.0.8Compare Source
Patch Changes
#1809
179b437- Fix lint-staged discarding the ongoing merge conflict status (.git/MERGE_HEAD) when using the--hide-unstagedor--hide-alloptions.#1811
3d0b2c0- Fix issues with Git commands that are successful but also emit warnings tostderr, by ignoring thestderroutput completely when the process exits with code 0. This was the behavior when usingnano-spawnandexeca, but when switching totinyexecin 16.3.0 bothstdoutandstderrwere used as interleaved output.v17.0.7Compare Source
Patch Changes
e692e58- Update dependencytinyexec@^1.2.4.v17.0.6Compare Source
Patch Changes
#1803
bdf2770- Run all tests with Deno, in addition to Node.js and Bun.#1796
7508272- Fix performance regression of lint-staged v17 by going back to usinggit addto stage task modifications. This was changed togit update-index --againin v17 for less manual work, but unfortunately theupdate-indexcommand gets slower in very large Git repos.#1797
7b2505a- This version of lint-staged uses the new staged publishing for npm packages feature. Releases are already published from GitHub Actions with trusted publishing, but now an additional approval with two-factor authentication is also required.#1802
321b0a9- Downgrade dependencytinyexec@1.2.2to avoid issues in version 1.2.3.v17.0.5Compare Source
Patch Changes
1f67271- Correctly set the--max-arg-lengthdefault value based on the running platform. This controls how very long lists of staged files are split into multiple chunks.v17.0.4Compare Source
Patch Changes
#1788
f95c1f8- Another fix for making sure lint-staged adds task modifications correctly to the commit in the following cases:<file>it is staged withgit add <file>, and then committed withgit commit<file>it is committed withgit commit --allwithout explicitgit add<file>it is committed withgit commit <pathspec>without explicitgit addThere's new test cases which actually setup the Git
pre_commithook to run lint-staged and verify them. These issues started in v17.0.0 when trying to improve support for committig without having explicitly staged files.v17.0.3Compare Source
Patch Changes
06813f9Thanks @iiroj! - Fix lint-staged behavior when implicitly committing files without usinggit addby either:git commit -am "my commit message"where-a(--all) means to automatically stage all tracked modified and deleted filesgit commit -m "my commit message" .where.is an example of a pathspec where matching files will be stagedv17.0.2Compare Source
Patch Changes
88670caThanks @iiroj! - Enable immutable GitHub releasesv17.0.1Compare Source
Patch Changes
4a5664bThanks @iiroj! - Adjust GitHub Actions workflow so that automatic publishing works with signed commits.v17.0.0Compare Source
Major Changes
#1745
e244adfThanks @iiroj! - Node.js v20 is no longer supported, and the oldest supported version is now22.22.1, which is an active LTS version at the time of this release. Node.js 20 will be EOL after April 2026. Please upgrade your Node.js version!#1676
0584e0bThanks @outslept! - Lint-staged now tries to verify the installed Git version is at least2.32.0, released in 2021. If you're using an even older Git version, you need to upgrade it before running lint-staged!#1745
2dcc40aThanks @iiroj! - The dependencyyamlis now marked as optional and probably won't be installed by default. If you're using a YAML configuration file you should install the package separately:If you're using
.lintstagedrcas the config file name (without a file extension), it will be treated as a YAML file. If the content is JSON, consider renaming it to.lintstagedrc.jsonto avoid needing to installyaml.Minor Changes
#1748
809d5efThanks @iiroj! - Add new option--hide-allfor hiding all unstaged changes and untracked files, before running tasks. This makes it easier to run tools like Knip which check for unused code. Untracked files are included in the backup stash and restored automatically after running.#1759
f13045aThanks @iiroj! - Update dependencies, includingtinyexec@1.1.1to fix the following issues:#!/usr/bin/env nodeshebang (Prettier, ESLint, for example) were previously spawned using the default Node.js version configured by the version manager (the onewhich nodepoints to) on POSIX systems. Now, they will be spawned with the same version that lint-staged itself was started with.nodeexecutable available inPATHis a symlink pointing to Snap itself. The sandboxing features of Snap prevented lint-staged from spawning scripts with the#!/usr/bin/env nodeshebang, because it meant lint-staged tried to spawn Snap via the symlink. This resulted in anENOENTerror when trying to runprettier, for example. Now, since the realnodeexecutable's directory is available in thePATH, lint-staged will instead spawn the script with the realnodebinary succesfully.#1761
d3251b1Thanks @iiroj! - Lint-staged now runsgit update-index --againafter running tasks, instead ofgit add <originally staged files>. This should improve compatibility when using non-default indexes, for example when committing with a pathspecgit commit -m "message" .instead of adding files to the index.#1745
a9585acThanks @iiroj! - Removecommanderas a dependency and use the built-inparseArgsfromnode:utilto parse CLI flags.Patch Changes
#1755
c82d30bThanks @iiroj! - All tests now pass on the Bun runtime (latest).#1750
a401818Thanks @iiroj! - Remove manual handling forgit stash --keep-indexresurrecting deleted files, because the issue was fixed in Git2.23.0and lint-staged requires at least Git2.32.0.#1771
c4b8936Thanks @iiroj! - Fix documentation about multiple config files and the--cwdoption. When using it, all tasks will be run in the specified directory. For example, to run everything in the actualprocess.cwd(), uselint-staged --cwd=".".microsoft/TypeScript (typescript)
v7.0.2Compare Source
v6.0.3: TypeScript 6.0.3Compare Source
For release notes, check out the release announcement blog post.
Downloads are available on:
qmhc/unplugin-dts (vite-plugin-dts)
v5.0.3Compare Source
v5.0.2Compare Source
v5.0.1Compare Source
v5.0.0Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.