Skip to content
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

chore(deps): update all non-major dependencies #2

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 1, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@antfu/eslint-config ^0.38.5 -> ^0.43.0 age adoption passing confidence
@vitest/coverage-c8 (source) ^0.30.1 -> ^0.33.0 age adoption passing confidence
esno ^0.16.3 -> ^0.17.0 age adoption passing confidence
pnpm (source) 8.1.1 -> 8.15.8 age adoption passing confidence
vitest (source) ^0.30.1 -> ^0.34.0 age adoption passing confidence

Release Notes

antfu/eslint-config (@​antfu/eslint-config)

v0.43.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.43.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.42.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.42.0

Compare Source

   🚀 Features
    View changes on GitHub

v0.41.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.41.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.41.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.41.1

Compare Source

   🚀 Features
    View changes on GitHub

v0.41.0

Compare Source

   🚀 Features
  • Do not auto fix unused-imports/no-unused-imports in editors  -  by @​antfu (ed2b0)
    View changes on GitHub

v0.40.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.40.2

Compare Source

No significant changes

    View changes on GitHub

v0.40.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.40.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.39.8

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.39.7

Compare Source

   🚀 Features
    View changes on GitHub

v0.39.6

Compare Source

   🚀 Features
    View changes on GitHub

v0.39.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
  • Disable @typescript-eslint/consistent-type-assertions  -  by @​antfu (abf5c)
    View changes on GitHub

v0.39.4

Compare Source

   🚀 Features
    View changes on GitHub

v0.39.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.39.2

Compare Source

   🚀 Features
    View changes on GitHub

v0.39.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.39.0

Compare Source

   🚀 Features
    View changes on GitHub

v0.38.6

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
vitest-dev/vitest (@​vitest/coverage-c8)

v0.33.0

Compare Source

   🚨 Breaking Changes
  • Revert default include patterns  -  by @​so1ve #​3729
    • 0.32.0 changed the default include globs to be compatible with Jest. After a discussion with the community, we are reverting this change because it turned out to be non-intuitive.
   🐞 Bug Fixes
    View changes on GitHub

v0.32.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.32.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.32.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.32.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.32.0

Compare Source

   🚨 Breaking Changes
  • Throw an error, if the module cannot be resolved  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3307 (1ad63)
    • Vitest used to fall back to the original import when it could not resolve it to the file path or the virtual module. This leads to hard-to-find module graph mismatches if you had incorrect alias or relied on relative imports to be resolved to the project root (which is usual behavior in TypeScript) because the code accidentally "worked". With this release, Vitest will now throw an error if it cannot resolve the module - there are possible edge cases that are not covered yet, so if you have any problems with this, please open a separate issue with reproduction.
  • Improve globs  -  by @​nickmccurdy in https://github.com/vitest-dev/vitest/issues/3392 (19ecc)
    • Vitest now has glob patterns similar to Jest for better compatibility. It's possible that some files will be considered test files when previously they were not. For example, Vitest now considers test.js to be a test file. Also any file in __tests__ is now considered to be a test, not just files with test or spec suffix.
  • Add @vitest/coverage-v8 package  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3339 (82112)
    • Vitest now uses v8 code coverage directly for better performance. @vitest/coverage-c8 is deprecated as Vitest no longer uses c8 package for coverage output. It will not be updated anymore, and Vitest will fail in the next version if the user has c8 as their coverage provider. Please, install the new @vitest/coverage-v8 package if you previously used @vitest/coverage-c8.
  • mocker: Don't restore mock to the original if the module is automocked  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3518 (c1004)
    • spy.mockRestore on auto-mocked named exports will no longer restore their implementation to the actual function. This behavior better matches what Jest does.
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.0

Compare Source

   🚨 Breaking Changes

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - "before 4am on the first day of the month" (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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from d9e0957 to 76b0851 Compare July 11, 2023 02:27
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from e5031f0 to ead7e78 Compare July 18, 2023 17:59
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from b99e97a to 33daa91 Compare July 31, 2023 05:25
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from b2f4ef0 to 790d5bd Compare August 7, 2023 02:54
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 2e69a5e to 1127cd2 Compare September 1, 2023 05:52
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 1731440 to 4161382 Compare September 12, 2023 23:28
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 230dfe2 to 3cf66f7 Compare September 20, 2023 02:23
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from c13b435 to 575f391 Compare October 16, 2023 05:40
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 52dd51b to 58d4656 Compare November 2, 2023 11:54
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from e00bfa7 to 7eb6a55 Compare November 14, 2023 17:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from fdf9505 to 79bf2c0 Compare December 15, 2023 17:43
Copy link

coderabbitai bot commented Dec 15, 2023

Important

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in 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?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f205f51 to 2895d9d Compare January 6, 2024 14:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from a12f273 to f63d17d Compare February 2, 2024 02:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 6465c0a to 0601330 Compare February 20, 2024 05:58
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e2f0645 to 226b75f Compare March 21, 2024 02:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 226b75f to 538f446 Compare April 5, 2024 00:00
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 538f446 to b522428 Compare April 16, 2024 20:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b522428 to c502cce Compare May 3, 2024 02:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants