chore(deps-dev): bump jest and @types/jest

[dependabot]

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

Important

Bump jest and @types/jest versions in core/package.json and package.json.

• Dependencies:
  • Bump jest from ^29.7.0 to ^30.0.3 in core/package.json and package.json.
  • Bump @types/jest from ^29.5.14 to ^30.0.0 in core/package.json.

^{This description was created by for 506be7d. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 506be7d in 1 minute and 18 seconds. Click for details.

• Reviewed 34 lines of code in 2 files
• Skipped 1 files when reviewing.
• Skipped posting 3 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. core/package.json:26

• Draft comment:
  Bump @types/jest to ^30.0.0; verify that any code or tests using Jest types remain compatible.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

2. core/package.json:33

• Draft comment:
  Jest updated to ^30.0.3, but jest-runner remains at ^29.7.0; confirm if updating jest-runner is needed for compatibility.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the PR author to confirm if updating jest-runner is needed for compatibility. This is related to dependency versions, which the rules specify should not be commented on unless the versions are recognized and there's a specific suggestion. The comment does not provide a specific suggestion or recognized version issue, so it should be removed.

3. package.json:48

• Draft comment:
  Jest bumped to ^30.0.3 here; consider aligning related packages (e.g., jest-environment-jsdom at ^29.7.0) to avoid potential version mismatches.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50% While the comment identifies a real version mismatch, this falls under dependency management which is explicitly mentioned in the rules as something we should not comment on. The rules state "Do NOT comment on dependency changes, library versions that you don't recognize, or anything else related to dependencies." Additionally, if this were a real issue, it would likely be caught by the build system. The version mismatch could potentially cause real runtime issues that might not be immediately apparent in the build process. Jest major version changes could have breaking changes. Even if there are potential issues, the rules explicitly state not to comment on dependency-related matters. Package managers and build systems are better suited to catch real compatibility issues. The comment should be deleted as it violates the rule about not commenting on dependency changes, regardless of its technical merit.

Workflow ID: wflow_2oJnWXgUJMyMW34R

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