Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 13, 2025

This PR contains the following updates:

Package Change Age Confidence
zod (source) ^3 -> ^3 || ^4.0.0 age confidence
zod (source) 3.25.65 -> 4.0.14 age confidence

Release Notes

colinhacks/zod (zod)

v4.0.14

Compare Source

Commits:

v4.0.13

Compare Source

v4.0.12

Compare Source

Commits:

v4.0.11

Compare Source

Commits:

v4.0.10

Compare Source

v4.0.9

Compare Source

Commits:

v4.0.8

Compare Source

Commits:

v4.0.7

Compare Source

v4.0.6

Compare Source

v4.0.5

Compare Source

v4.0.4

Compare Source

v4.0.3

Compare Source

v4.0.2

Compare Source

v4.0.1

Compare Source

Commits:

v4.0.0

Compare Source

v3.25.76

Compare Source

v3.25.75

Compare Source

v3.25.74

Compare Source

v3.25.73

Compare Source

Commits:

v3.25.72

Compare Source

v3.25.71

Compare Source

v3.25.70

Compare Source

v3.25.69

Compare Source

v3.25.68

Compare Source

v3.25.67

Compare Source

Commits:

v3.25.66

Compare Source


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

@renovate
Copy link
Contributor Author

renovate bot commented Jul 13, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @clipboard-health/example-nestjs@0.0.10
npm error Found: zod@4.0.14
npm error node_modules/zod
npm error   zod@"4.0.14" from @clipboard-health/example-nestjs@0.0.10
npm error   packages/example-nestjs
npm error     @clipboard-health/example-nestjs@0.0.10
npm error     node_modules/@clipboard-health/example-nestjs
npm error       workspace packages/example-nestjs from the root project
npm error
npm error Could not resolve dependency:
npm error peer zod@"^3" from @clipboard-health/contract-core@0.17.0
npm error node_modules/@clipboard-health/contract-core
npm error   @clipboard-health/contract-core@"0.17.0" from @clipboard-health/example-nestjs@0.0.10
npm error   packages/example-nestjs
npm error     @clipboard-health/example-nestjs@0.0.10
npm error     node_modules/@clipboard-health/example-nestjs
npm error       workspace packages/example-nestjs from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-08-02T08_03_50_361Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-08-02T08_03_50_361Z-debug-0.log

@coderabbitai
Copy link
Contributor

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

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

PR Summary

Updates Zod dependency from v3 to v4 across core packages, bringing significant performance improvements and breaking changes in error handling.

  • Multiple packages updated to support both Zod v3 and v4 (^3 || ^4.0.0) in peer dependencies
  • Direct dependency version bumped from 3.25.65 to 4.0.2 in packages/config, packages/contract-core, and other packages
  • Notable v4 improvements include 3x faster parsing and 57% smaller bundle size
  • Breaking changes in error customization APIs and coercion behavior require careful testing
  • Follows recommended migration path for library authors with dual version support

6 files reviewed, no comments
Edit PR Review Bot Settings | Greptile

@renovate renovate bot force-pushed the renovate/zod-4.x branch 2 times, most recently from 4a964e2 to e627d2c Compare July 14, 2025 02:46
@stale
Copy link

stale bot commented Jul 21, 2025

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the wontfix This will not be worked on label Jul 21, 2025
@renovate renovate bot force-pushed the renovate/zod-4.x branch 6 times, most recently from de378ce to ec27ee9 Compare August 1, 2025 12:36
@renovate renovate bot force-pushed the renovate/zod-4.x branch from ec27ee9 to 7343b36 Compare August 2, 2025 08:03
@renovate
Copy link
Contributor Author

renovate bot commented Aug 6, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/zod-4.x branch August 6, 2025 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

wontfix This will not be worked on

Development

Successfully merging this pull request may close these issues.

2 participants