coderabbitai[bot]
commented
3 months ago [!IMPORTANT]
Review skipped
Auto reviews are limited to specific labels.
Please check the settings in the CodeRabbit UI or the
.coderabbit.yamlfile in this repository. To trigger a single review, invoke the@coderabbitai reviewcommand.You can disable this status message by setting the
reviews.review_statustofalsein the CodeRabbit configuration file.
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ rimraf (5.0.8 → 6.0.1) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 8 commits:
6.0.1load version with package-json-from-distfeat: add --version flag for CLIchore: add `/.tap` to .gitignore6.0.0drop dead node versions5.0.9restore support for dead node versions↗️ foreground-child (indirect, 3.1.1 → 3.2.1) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 8 commits:
3.2.1stdout/stderr is always null, reflect in return typeno need for .d.ts or .map for test fixturesdon't fail make clean if already clean3.2.0update deps, clean up tests, add exportsremove FUNDING.yml (coming from .github repo now)add github link to typedocs↗️ jackspeak (indirect, 2.3.6 → 4.0.1) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 42 commits:
4.0.1put back the cleaner code node 14 can't handle4.0.0changelog updates3.4.2restore support for 14.latest and 16.latest3.4.1node 14 no longer supported3.4.0abstract out post-parse actions, slice process.argv in parseRaw3.3.0stopAtPositionalTest3.2.6add hint to toJSON output3.2.5Revert "Infer 'validOptions' all the way through"3.2.4Infer 'validOptions' all the way through, when possible3.2.3more code fencing issues3.2.2tighter code fenced blocks in usage3.2.1do not whitespace-normalize fenced code blocks3.2.0add parseRaw() method, to parse without side effectsfix: still validate if stopAtPositional is setformat, remove unused .d.ts file3.1.2mark validOptions readonly so we can infer from itmention validate() signature change in changelog3.1.1loosen types on *List methodsci: drop node 16, 18changelog 3.13.1.0Add 'validOptions' array for validation3.0.0changelog 3.0move custom error fields to 'cause' propertyci: remove v14, makeworkremove FUNDING.yml (coming from .github repo now)↗️ minipass (indirect, 7.0.4 → 7.1.2) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 11 commits:
7.1.2update devDeps, loosen constructor argument type7.1.1fix: use `node:`-prefixed requires for builtinsnpm audit fix7.1.0update write/end types to comply with NodeJS.WritableStreamremove FUNDING.yml (coming from .github repo now)remove unused fixup script and sync-content deptest: windows paths are too url-likeremove makework gh action jobs↗️ path-scurry (indirect, 1.10.1 → 2.0.0) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 23 commits:
2.0.0modernize, drop support for old node versionsci: remove makework jobci: update node versionsactually deprecate deprecated Path.path getter1.11.1engines: need 14.18, where 'node:path' shows up1.11.0changelog 1.11add isCWD, correct relative() when cwd is rootupdate prettier, reformat1.10.4fix: use `node:`-prefixed requires for builtinsupdate word-wrap for advisory fix1.10.3update tshy, remove unnecessary rm in buildAdd parentPath to PathBaseUpdate to latest @types/node1.10.2correctly readlink() when in multiply-nested symlink dirsupdate dev depsremove FUNDING.yml (coming from .github repo now)add github link to typedocs🆕 package-json-from-dist (added, 1.0.0)
👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands