Skip to content

fix(deps): update all dependencies #467

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

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

fix(deps): update all dependencies #467

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 10, 2025

This PR contains the following updates:

Package Change Age Confidence Type Update
@1stg/eslint-config (source) ^9.0.6 -> ^10.0.0 age confidence devDependencies major
@types/jest (source) ^29.5.14 -> ^30.0.0 age confidence devDependencies major
autofix-ci/action 2891949 -> 635ffb0 action digest
codecov/codecov-action v5.4.2 -> v5.4.3 age confidence action patch
eslint-plugin-jest ^28.11.0 -> ^29.0.0 age confidence devDependencies major
find-up ^5.0.0 -> ^7.0.0 age confidence dependencies major
glob ^10.4.5 -> ^11.0.0 age confidence dependencies major
jest (source) ^29.7.0 -> ^30.0.0 age confidence devDependencies major
node (source) 22.15.0 -> 22.17.1 age confidence minor
pify ^5.0.0 -> ^6.0.0 age confidence devDependencies major
yargs (source) ^17.7.2 -> ^18.0.0 age confidence dependencies major
yarn (source) 4.9.1 -> 4.9.2 age confidence packageManager patch

Release Notes

1stG/configs (@​1stg/eslint-config)

v10.2.0

Compare Source

Minor Changes
Patch Changes

v10.1.0

Compare Source

Minor Changes
Patch Changes

v10.0.0

Compare Source

Major Changes

v9.1.0

Compare Source

Minor Changes
codecov/codecov-action (codecov/codecov-action)

v5.4.3

Compare Source

What's Changed

Full Changelog: https://github.com/codecov/codecov-action/compare/v5.4.2..v5.4.3

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 (d3bf1dc)
Features
  • drop support for [@typescript-eslint](https://redirect.github.com/typescript-eslint) v6 (fe61a40)
  • drop support for [@typescript-eslint](https://redirect.github.com/typescript-eslint) v7 (5ca65d3)
  • drop support for ESLint v7 (b06e7d0)
  • drop support for ESLint v8.x prior to v8.57.0 (d79765a)
  • drop support for Node v16 (aaf62cd)
  • drop support for Node v18 (598880c)
  • drop support for Node v20.x prior to v20.12.0 (2f2fb68)
  • drop support for Node v21 (a366393)
  • drop support for Node v23 (1fb1a67)
  • unbound-method: remove docs.recommended and docs.requiresTypeChecking properties (945651c)
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)

v28.13.3

Compare Source

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

v28.13.2

Compare Source

Bug Fixes

v28.13.1

Compare Source

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

v28.13.0

Compare Source

Features

v28.12.0

Compare Source

Features
  • no-disabled-tests: improve error message and simplify rule (#​1739) (1fb5a4a)

28.11.2 (2025-05-29)

Bug Fixes

28.11.1 (2025-05-27)

Bug Fixes
  • no-large-snapshots: use a far better message for when an unexpected snapshot is found (#​1736) (0f5b873)

v28.11.2

Compare Source

Bug Fixes

v28.11.1

Compare Source

Bug Fixes
  • no-large-snapshots: use a far better message for when an unexpected snapshot is found (#​1736) (0f5b873)
sindresorhus/find-up (find-up)

v7.0.0

Compare Source

Breaking
Improvements
  • Accept URL for stopAt option ba19153

v6.3.0

Compare Source

v6.2.0

Compare Source

v6.1.0

Compare Source

v6.0.0

Compare Source

Breaking
  • Require Node.js 12.20 e93cfd2
  • This package is now pure ESM. Please read this.
  • Changed from a default export to named exports.
    • const findUp = require('find-up') => import {findUp} from 'find-up'
    • const findUpSync = require('find-up').sync => import {findUpSync} from 'find-up'
    • const findUpStop = require('find-up').stop => import {findUpStop} from 'find-up'
    • const pathExists = require('find-up').exists => import {pathExists} from 'find-up'
    • const pathExistsSync = require('find-up').sync.exists => import {pathExistsSync} from 'find-up'
isaacs/node-glob (glob)

v11.0.3

Compare Source

v11.0.2

Compare Source

v11.0.1

Compare Source

v11.0.0

Compare Source

jestjs/jest (jest)

v30.0.4

Compare Source

Features
  • [expect] The Inverse type is now exported (#​15714)
  • [expect] feat: support async functions in toBe (#​15704)
Fixes
  • [jest] jest --onlyFailures --listTests now correctly lists only failed tests (#​15700)
  • [jest-snapshot] Handle line endings in snapshots (#​15708)

v30.0.3

Compare Source

Fixes
  • [jest-config] Fix ESM TS config loading in a CJS project (#​15694)
Features
  • [jest-diff] Show non-printable control characters to diffs (#​15696)

v30.0.2

Compare Source

v30.0.1

Compare Source

v30.0.0

Compare Source

nodejs/node (node)

v22.17.1

Compare Source

v22.17.0: 2025-06-24, Version 22.17.0 'Jod' (LTS), @​aduh95

Compare Source

Notable Changes
⚠️ Deprecations
Instantiating node:http classes without new

Constructing classes like IncomingMessage or ServerResponse without the new
keyword is now discouraged. This clarifies API expectations and aligns with standard
JavaScript behavior. It may warn or error in future versions.

Contributed by Yagiz Nizipli in #​58518.

options.shell = "" in node:child_process

Using an empty string for shell previously had undefined behavior. This change
encourages explicit choices (e.g., shell: true or a shell path) and avoids
relying on implementation quirks.

Contributed by Antoine du Hamel and Renegade334 #​58564.

HTTP/2 priority signaling

The HTTP/2 prioritization API (e.g., stream.priority) is now deprecated due to
poor real-world support. Applications should avoid using priority hints and expect future removal.

Contributed by Matteo Collina and Antoine du Hamel #​58313.

✅ Features graduated to stable
assert.partialDeepStrictEqual()

This method compares only a subset of properties in deep object comparisons,
useful for flexible test assertions. Its stabilization means it's now safe for
general use and won't change unexpectedly in future releases.

Contributed by Ruben Bridgewater in #​57370.

Miscellaneous
  • dirent.parentPath
  • filehandle.readableWebStream()
  • fs.glob()
  • fs.openAsBlob()
  • node:readline/promises
  • port.hasRef()
  • readable.compose()
  • readable.iterator()
  • readable.readableAborted
  • readable.readableDidRead
  • Duplex.fromWeb()
  • Duplex.toWeb()
  • Readable.fromWeb()
  • Readable.isDisturbed()
  • Readable.toWeb()
  • stream.isErrored()
  • stream.isReadable()
  • URL.createObjectURL()
  • URL.revokeObjectURL()
  • v8.setHeapSnapshotNearHeapLimit()
  • Writable.fromWeb()
  • Writable.toWeb()
  • writable.writableAborted
  • Startup Snapshot API
  • ERR_INPUT_TYPE_NOT_ALLOWED
  • ERR_UNKNOWN_FILE_EXTENSION
  • ERR_UNKNOWN_MODULE_FORMAT
  • ERR_USE_AFTER_CLOSE

Contributed by James M Snell in
#​57513 and
#​58541.

Semver-minor features
🔧 fs.FileHandle.readableWebStream gets autoClose option

This gives developers explicit control over whether the file descriptor should
be closed when the stream ends. Helps avoid subtle resource leaks.

Contributed by James M Snell in #​58548.

🔧 fs.Dir now supports explicit resource management

This improves ergonomics around async iteration of directories. Developers can
now manually control when a directory is closed using .close() or with Symbol.asyncDispose.

Contributed by Antoine du Hamel in #​58206.

📊 http2 gains diagnostics channel: http2.server.stream.finish

Adds observability support for when a stream finishes. Useful for logging,
monitoring, and debugging HTTP/2 behavior without patching internals.

Contributed by Darshan Sen in #​58560.

🔐 Permissions: implicit allow-fs-read to entrypoint

Node.js permissions model now allows read access to the entry file by default.
It makes running permission-restricted apps smoother while preserving security.

Contributed by Rafael Gonzaga in #​58579.

🎨 util.styleText() adds 'none' style

This lets developers remove styling cleanly without hacks. Useful for overriding
inherited terminal styles when composing styled strings.

Contributed by James M Snell in #​58437.

🧑‍💻 Community updates
Commits

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.

Copy link

changeset-bot bot commented Jul 10, 2025

⚠️ No Changeset found

Latest commit: 8b195d2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

Copy link

codesandbox-ci bot commented Jul 10, 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

pkg-pr-new bot commented Jul 10, 2025

Open in StackBlitz

npm i https://pkg.pr.new/prettier-eslint-cli@467

commit: 8b195d2

Copy link

coderabbitai bot commented Jul 10, 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

@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 36f0b1f in 2 minutes and 18 seconds. Click for details.
  • Reviewed 97 lines of code in 5 files
  • Skipped 2 files when reviewing.
  • Skipped posting 13 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:40
  • Draft comment:
    Updated autofix-ci action digest to 635ffb0c9798bd160680f18fd73371e355b85f27. Please verify that this update remains compatible with your workflow and does not introduce any unexpected behavior.
  • 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 verify compatibility and check for unexpected behavior, which violates the rule against asking for confirmation or verification. It does not provide a specific suggestion or point out a specific issue.
2. .github/workflows/ci.yml:43
  • Draft comment:
    Codecov action has been updated to digest 18283e04ce6e62d37312384ff67231eb8fd56d24 (v5.4.3). Review the changelog to ensure the changes (e.g. OIDC fixes) do not impact your coverage reporting.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative and asks the PR author to review the changelog, which violates the rules against making purely informative comments and asking the author to double-check things.
3. .nvmrc:1
  • Draft comment:
    Node version updated to 22.17.0. Confirm that this aligns with the project's engine requirements and that all dependencies are compatible with this version.
  • 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 compatibility with the project's engine requirements and dependencies, which violates the rule against asking for confirmation or ensuring compatibility. It does not provide a specific suggestion or point out a specific issue.
4. .yarnrc.yml:10
  • Draft comment:
    Yarn path updated to use yarn-4.9.2.cjs. Ensure that the new Yarn version is fully compatible with your build scripts and plugins.
  • 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 compatibility of the new Yarn version with build scripts and plugins, which falls under the rule of not asking the author to ensure or verify things. It does not provide a specific suggestion or point out a specific issue.
5. package.json:15
  • Draft comment:
    The packageManager field has been updated to '[email protected]'. This change is consistent with the Yarn upgrade in .yarnrc.yml. Confirm that this version suits the project's requirements.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is related to a dependency change, specifically the package manager version. It asks the author to confirm if the version suits the project's requirements, which is against the rules. The comment does not provide a specific suggestion or highlight a potential issue with the change.
6. package.json:59
  • Draft comment:
    Dependency 'find-up' has been updated to ^7.0.0. Note that version 7 is now pure ESM and requires Node 18+. Since the project is CommonJS-based, verify that the way 'find-up' is imported and used remains compatible.
  • Reason this comment was not posted:
    Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% The comment raises a valid compatibility concern, but the project already requires Node 18+ and explicitly declares itself as CommonJS. The package.json shows this is a well-maintained project with careful version management. The maintainers likely knew what they were doing with this update. The comment identifies a real technical consideration. Maybe the maintainers weren't aware of the ESM change? The project's explicit CommonJS type and Node version requirements suggest this was an intentional update with awareness of the implications. Delete the comment. It violates the rule about not asking for verification, and the project setup suggests the maintainers are already aware of the compatibility requirements.
7. package.json:60
  • Draft comment:
    Dependency 'glob' has been updated to ^11.0.0. Review its changelog for any breaking changes affecting glob patterns or its API.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is about a dependency change and suggests reviewing the changelog for breaking changes. According to the rules, comments on dependency changes should be ignored, especially if they are about versions or changelogs.
8. package.json:65
  • Draft comment:
    Dependency 'yargs' has been updated to ^18.0.0. Check for any major changes in the API that might affect command-line parsing in the CLI.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is about a dependency update, specifically 'yargs', and suggests checking for major changes in the API. This falls under the rule of not commenting on dependency changes or library versions that are not recognized. The comment does not provide a specific suggestion or point out a specific issue with the code.
9. package.json:68
  • Draft comment:
    Updated '@1stg/eslint-config' to ^10.0.0. This major bump may include breaking changes in ESLint rules/configurations, so verify that linting behaves as expected.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is about a dependency update and suggests verifying the behavior, which violates the rules. It doesn't provide a specific code suggestion or ask for a specific test to be written.
10. package.json:76
  • Draft comment:
    Updated '@types/jest' to ^30.0.0. Ensure that the new type definitions are compatible with your existing tests.
  • 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 updating the '@types/jest' package. The comment asks the author to ensure compatibility, which is against the rules. Therefore, this comment should be removed.
11. package.json:80
  • Draft comment:
    Updated 'eslint-plugin-jest' to ^29.0.0. Review the plugin's changelog for rule adjustments or deprecated features that might affect your tests.
  • 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 updating a plugin version. It suggests reviewing the changelog for potential issues, which falls under the category of asking the author to double-check things. This violates the rule against commenting on dependency changes or asking the author to ensure behavior is intended.
12. package.json:82
  • Draft comment:
    Updated 'jest' to ^30.0.0. Since this is a major version bump, run your test suite to ensure no regressions or breaking changes have been introduced.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is about a dependency update and suggests running tests to ensure no regressions. It violates the rule against commenting on dependency changes and asking the author to ensure the change is tested.
13. package.json:86
  • Draft comment:
    Updated 'pify' to ^6.0.0. Verify that any changes in its API are properly handled in the code.
  • 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 verify changes in the API of a dependency, which is not allowed according to the rules. It does not provide a specific suggestion or point out a specific issue.

Workflow ID: wflow_Z4EEXq7l5QmKdcVe

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

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.

0 participants