chore: upgrade zod to 4.5.4

[JAIVIGNESH2002]

UpgradePilot verified zod from 3.25.76 to 4.5.4.

Verification evidence:

• Create sandbox: TrueForge deterministic sandbox
• Clone repository: git clone --depth 1 https://github.com/JAIVIGNESH2002/SiftLane /opt/tf/tool-results/upgradepilot-upgrade-worktree/repo
• Install target dependency: npm install zod@4.5.4
• Repair and re-verify: TrueForge repair agent + deterministic verification

[qodo-code-review]

PR Summary by Qodo

Upgrade Zod to 4.5.4 and migrate validation APIs

⚙️ Configuration changes 🐞 Bug fix 🕐 10-20 Minutes

AI Description

• Upgrades Zod from 3.25.76 to 4.5.4.
• Migrates validation schemas and error handling to Zod 4 APIs.
• Preserves existing feed and article-state validation behavior.

Diagram

graph TD
  Manifest["Package manifest"] --> Lockfile["Dependency lockfile"] --> Zod["Zod 4.5.4"] --> Validation["Validation schemas"] --> Consumers["Application consumers"]

Loading

High-Level Assessment

The focused in-place migration is appropriate: it upgrades the dependency while adapting only the Zod 4 breaking API surfaces used by the project. A compatibility wrapper or dual-version strategy would add unnecessary complexity for this small validation module.

Files changed (3) +9 / -10

Bug fix (1) +4 / -5

validation.tsMigrate validation logic to Zod 4 APIs +4/-5

Migrate validation logic to Zod 4 APIs

• Replaces legacy string error options with the unified message option, supplies explicit record key and value schemas, and reads validation failures from ZodError.issues. Existing user-facing validation behavior remains intact.

src/lib/validation.ts

Other (2) +5 / -5

package-lock.jsonResolve and pin Zod 4.5.4 +4/-4

Resolve and pin Zod 4.5.4

• Updates the root dependency specification and resolved package metadata from Zod 3.25.76 to 4.5.4, including the registry URL and integrity hash.

package-lock.json

package.jsonUpgrade the Zod dependency range +1/-1

Upgrade the Zod dependency range

• Changes the application dependency from an exact Zod 3.25.76 version to the compatible Zod 4 range beginning at 4.5.4.

package.json

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Non-string URL mislabeled missing 🐞 Bug ≡ Correctness

Description

Replacing both URL error options with one message makes every string type failure say “Feed URL is
required,” including a submitted File or other non-string value that should say “Feed URL must be
text.” This regresses the schema’s prior distinction and returns the wrong validation feedback from
addFeedAction.

Code

src/lib/validation.ts[6]

+      message: "Feed URL is required.",

Evidence

The changed schema supplies a single message for z.string, while addFeedAction passes the raw
FormData.get("url") result into it and returns the resulting issue text directly. The official Zod
4 migration guide explicitly shows that preserving separate required and invalid-type messages
requires an error function branching on issue.input === undefined.

src/lib/validation.ts[3-8]
src/app/actions.ts[23-30]
🌐 Zod 4 dropped required_error and invalid_type_error; its migration example preserves their distinction with error: issue => issue.input === undefined ? requiredMessage : invalidTypeMessage.

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Preserve the separate required and invalid-type messages when migrating the URL schema to Zod 4.

## Issue Context
Zod 4 replaces `required_error` and `invalid_type_error` with an `error` callback that can inspect whether `issue.input` is `undefined`. A single `message` applies the required message to all invalid input types.

## Fix Focus Areas
- src/lib/validation.ts[4-8]
- test/validation.test.ts[16-23]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Context sources

✅ Web pages:

  🌐 Migration guide | Zod

  🌐 Release notes | Zod

  🌐 packages/docs/content/v4/changelog.mdx

  +2 more

Review mode: ⚖️ Balanced: This dependency upgrade changes runtime validation behavior for Zod 4 across multiple schema and error-handling sites, so it warrants a careful single-pass review.

Tip of the day

💡 Did you know, you can enable the Remediation agent and Qodo fixes findings in a dedicated fix PR

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-code-review]

1. Non-string url mislabeled missing 🐞 Bug ≡ Correctness

Replacing both URL error options with one message makes every string type failure say “Feed URL is
required,” including a submitted File or other non-string value that should say “Feed URL must be
text.” This regresses the schema’s prior distinction and returns the wrong validation feedback from
addFeedAction.

Agent Prompt

## Issue description
Preserve the separate required and invalid-type messages when migrating the URL schema to Zod 4.

## Issue Context
Zod 4 replaces `required_error` and `invalid_type_error` with an `error` callback that can inspect whether `issue.input` is `undefined`. A single `message` applies the required message to all invalid input types.

## Fix Focus Areas
- src/lib/validation.ts[4-8]
- test/validation.test.ts[16-23]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools