Skip to content

fix(deps): update all dependencies #400

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

Merged
merged 4 commits into from
Jun 26, 2025
Merged

fix(deps): update all dependencies #400

merged 4 commits into from
Jun 26, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 26, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@1stg/nano-staged (source) ^0.2.0 -> ^0.3.0 age adoption passing confidence devDependencies minor
@types/jest (source) ^29.5.14 -> ^30.0.0 age adoption passing confidence devDependencies major
autofix-ci/action 2891949 -> 635ffb0 action digest
eslint-plugin-jest ^28.13.3 -> ^29.0.0 age adoption passing confidence devDependencies major
hermes-eslint ^0.28.1 -> ^0.29.0 age adoption passing confidence devDependencies minor
stable-hash-x ^0.1.1 -> ^0.2.0 age adoption passing confidence dependencies minor

Release Notes

1stG/configs (@​1stg/nano-staged)

v0.3.0

Compare Source

Minor Changes
Patch Changes

v0.2.1

Compare Source

Patch Changes
jest-community/eslint-plugin-jest (eslint-plugin-jest)

v29.0.1

Compare Source

Bug Fixes
  • update semantic-release config so new v29 major is marked as latest on npm (#​1772) (531c8ba)

v29.0.0

Compare Source

Bug Fixes
  • remove jest/no-alias-methods from styles config (df3b8cd)
  • update semantic-release config so new v29 major is marked as latest on npm (#​1772) (531c8ba)
Features
  • drop support for [@typescript-eslint](https://redirect.github.com/typescript-eslint) v6 (fbf49a0)
  • drop support for [@typescript-eslint](https://redirect.github.com/typescript-eslint) v7 (d77ac46)
  • drop support for ESLint v7 (60e26c2)
  • drop support for ESLint v8.x prior to v8.57.0 (854cef4)
  • drop support for Node v16 (8000c3d)
  • drop support for Node v18 (f442a2a)
  • drop support for Node v20.x prior to v20.12.0 (83c130b)
  • drop support for Node v21 (e6d5a25)
  • drop support for Node v23 (d7fe2d4)
  • unbound-method: remove docs.recommended and docs.requiresTypeChecking properties (1d53075)
BREAKING CHANGES
  • dropped support for ESLint v8.x prior to v8.57.0
  • dropped support for Node v20.x prior to v20.12.0
  • dropped support for Node v23
  • dropped support for Node v18
  • unbound-method: removed docs.recommend and docs.requiresTypeChecking from unbound-method
  • dropped support for @typescript-eslint v7
  • dropped support for @typescript-eslint v6
  • jest/no-alias-methods has been removed from the styles config as its already in
    the recommended config
  • dropped support for ESLint v7
  • dropped support for Node v21
  • dropped support for Node v16

v28.14.0

Compare Source

Features
  • unbound-method: mark docs.recommended and docs.requiresTypeChecking as deprecated (#​1762) (30440ef)

28.13.5 (2025-06-13)

Bug Fixes
  • handle string-based import names when resolving Jest functions (#​1761) (d8b5e0e)

28.13.4 (2025-06-13)

Bug Fixes
  • prefer-importing-jest-globals: handle string-based import names (#​1756) (547e67b)

28.13.3 (2025-06-10)

Bug Fixes
  • prefer-importing-jest-globals: preserve require property renames (#​1754) (41b9523)

28.13.2 (2025-06-10)

Bug Fixes

28.13.1 (2025-06-10)

Bug Fixes
  • prefer-ending-with-an-expect: don't report on await expect (#​1752) (5e3d687)

v28.13.5

Compare Source

Bug Fixes
  • handle string-based import names when resolving Jest functions (#​1761) (d8b5e0e)

v28.13.4

Compare Source

Bug Fixes
  • prefer-importing-jest-globals: handle string-based import names (#​1756) (547e67b)
un-ts/stable-hash-x (stable-hash-x)

v0.2.0

Compare Source

Minor Changes
Patch Changes

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (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.


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

This PR was generated by Mend Renovate. View the repository job log.


Important

Update dependencies and GitHub Actions in package.json and autofix.yml.

  • Dependencies:
    • Update stable-hash-x to ^0.2.0 in package.json.
    • Update @1stg/nano-staged to ^0.3.0, @types/jest to ^30.0.0, eslint-plugin-jest to ^29.0.1, hermes-eslint to ^0.29.0.
  • GitHub Actions:
    • Update autofix-ci/action to commit 635ffb0 in autofix.yml.

This description was created by Ellipsis for ba42850. You can customize this summary. It will automatically update as commits are pushed.

Copy link

changeset-bot bot commented Jun 26, 2025

🦋 Changeset detected

Latest commit: ba42850

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
eslint-plugin-import-x Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link

coderabbitai bot commented Jun 26, 2025

Important

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.


🪧 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>, please review it.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

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 using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

Copy link

codesandbox-ci bot commented Jun 26, 2025

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Copy link

socket-security bot commented Jun 26, 2025

Copy link

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Important

Looks good to me! 👍

Reviewed everything up to 7b80636 in 38 seconds. Click for details.
  • Reviewed 58 lines of code in 2 files
  • Skipped 1 files when reviewing.
  • Skipped posting 6 draft comments. View those below.
  • Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. .github/workflows/autofix.yml:34
  • Draft comment:
    Updated autofix-ci commit hash; ensure this revision (635ffb0c9798bd160680f18fd73371e355b85f27) is verified against the expected v1 release.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to ensure that a specific commit hash is verified against an expected release. This falls under the category of asking the author to double-check or verify something, which is against the rules.
2. package.json:87
  • Draft comment:
    Bump stable-hash-x from ^0.1.1 to ^0.2.0; verify that the new API (including any changes such as the added crossRealm option) is compatible with your usage.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is about a dependency change, specifically bumping the version of a library. The comment asks the author to verify compatibility, which is against the rules. Therefore, this comment should be removed.
3. package.json:92
  • Draft comment:
    Upgrade @1stg/nano-staged to ^0.3.0; review its changelog for any adjustments required in your configuration.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is about a dependency upgrade and suggests reviewing the changelog for adjustments. It doesn't provide a specific code suggestion or highlight a specific issue with the code. It falls under the category of purely informative comments about dependencies, which should be removed according to the rules.
4. package.json:121
  • Draft comment:
    Update @types/jest to ^30.0.0; confirm that the new type definitions don't introduce breaking changes in your tests.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to confirm that the new type definitions don't introduce breaking changes, which is against the rules. It is related to dependency changes, which should not be commented on unless it's a specific version mismatch or similar issue.
5. package.json:141
  • Draft comment:
    Upgrade eslint-plugin-jest to ^29.0.0; check for any breaking configuration changes as noted in its changelog.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is related to a dependency change, specifically upgrading a plugin version. The comment suggests checking for breaking changes, which falls under the rule of not asking the PR author to double-check things or ensure behavior. Therefore, this comment should be removed.
6. package.json:151
  • Draft comment:
    Update hermes-eslint to ^0.29.0; ensure this version doesn’t affect your ESLint setup.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is about updating a dependency version and asks the author to ensure it doesn't affect their setup. This falls under the rule of not commenting on dependency changes or asking the author to ensure something.

Workflow ID: wflow_BDfUKWEGkiBcv6FH

You can customize Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.

Copy link

pkg-pr-new bot commented Jun 26, 2025

Open in StackBlitz

npm i https://pkg.pr.new/eslint-plugin-import-x@400

commit: ba42850

Copy link

codacy-production bot commented Jun 26, 2025

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
+0.00% (target: -1.00%)
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (f91cb36) 3722 3561 95.67%
Head commit (ba42850) 3722 (+0) 3561 (+0) 95.67% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#400) 0 0 ∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

Copy link
Contributor Author

renovate bot commented Jun 26, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Copy link

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Important

Looks good to me! 👍

Reviewed 01dbc52 in 45 seconds. Click for details.
  • Reviewed 23 lines of code in 2 files
  • Skipped 0 files when reviewing.
  • Skipped posting 2 draft comments. View those below.
  • Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. .changeset/wet-toys-happen.md:5
  • Draft comment:
    The changeset file is well-formatted. Please confirm that a patch bump is appropriate for updating stable-hash-x from v0.1.1 to v0.2.0, as it's a minor dependency update.
  • Reason this comment was not posted:
    Confidence changes required: 33% <= threshold 50% None
2. .github/workflows/autofix.yml:34
  • Draft comment:
    The workflow comment now reads '# v1.3.2' but the commit hash remains unchanged from previous usage. Please verify that the pinned commit corresponds to v1.3.2 to avoid confusion.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the author to verify the commit hash, which is similar to asking them to double-check something. This violates the rule against asking the author to confirm or verify things. The comment does not provide a specific suggestion or point out a clear issue with the code itself.

Workflow ID: wflow_ApSVbZxSJq5RgVbz

You can customize Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.

Copy link

codecov bot commented Jun 26, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.10%. Comparing base (f91cb36) to head (ba42850).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #400   +/-   ##
=======================================
  Coverage   96.10%   96.10%           
=======================================
  Files          96       96           
  Lines        4951     4951           
  Branches     1859     1859           
=======================================
  Hits         4758     4758           
  Misses        192      192           
  Partials        1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Important

Looks good to me! 👍

Reviewed ba42850 in 41 seconds. Click for details.
  • Reviewed 20 lines of code in 1 files
  • Skipped 1 files when reviewing.
  • Skipped posting 2 draft comments. View those below.
  • Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. CHANGELOG.md:191
  • Draft comment:
    The removed empty line after the '- [#263] ...' entry may affect the consistency of the changelog's formatting. Please ensure that the removal aligns with your project's style guidelines for changelog entries.
  • Reason this comment was not posted:
    Confidence changes required: 33% <= threshold 50% None
2. CHANGELOG.md:209
  • Draft comment:
    Similarly, the deletion of the extra blank line after the '- [#248] ...' entry might impact readability. Verify that the changelog formatting remains consistent throughout the document.
  • Reason this comment was not posted:
    Confidence changes required: 33% <= threshold 50% None

Workflow ID: wflow_bZNidaT8aFB9tXye

You can customize Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.

@JounQin JounQin merged commit 34adb40 into master Jun 26, 2025
91 checks passed
@JounQin JounQin deleted the renovate/all branch June 26, 2025 07:13
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.

1 participant