Update zod-documentation extension

[ezzylan]

Description

• Updated the Zod documentation extension to include Zod 4
• Added the ability to toggle between Zod 4 and 3

Screencast

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Thank you for your contribution! 🎉

🔔 @danieldeichfuss you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

📋 Quick checkout commands

BRANCH="ext/zod-documentation"
FORK_URL="https://github.com/ezzylan/raycast-extensions.git"
EXTENSION_NAME="zod-documentation"
REPO_NAME="raycast-extensions"

git clone -n --depth=1 --filter=tree:0 -b $BRANCH $FORK_URL
cd $REPO_NAME
git sparse-checkout set --no-cone "extensions/$EXTENSION_NAME"
git checkout
cd "extensions/$EXTENSION_NAME"
npm install && npm run dev

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 10-15 business days.

[greptile-apps]

Greptile Summary

This PR updates the Zod documentation extension to support both Zod 4 and Zod 3, adds a version dropdown to toggle between them, and migrates the ESLint config to the v9 flat format.

• Adds Zod 4 doc data alongside existing Zod 3 data, with a flattenDocs(zodVersion) dispatcher that correctly routes to per-version URL builders (Zod 4 uses the current zod.dev domain; Zod 3 uses the v3 subdomain).
• Introduces a ZodVersionDropdown in the list's search bar accessory driven by local React state, fixing the earlier module-level snapshot issue.
• Removes the unused @raycast/utils dependency and replaces the legacy .eslintrc.json with an ESLint v9 flat config.

Confidence Score: 5/5

Safe to merge after the changelog date placeholder is corrected.

The core logic changes are correct — version-specific URLs are hardcoded per function rather than computed from a shared snapshot, so switching between Zod 3 and Zod 4 produces the right links. The only change needed is a one-word fix to the changelog date.

CHANGELOG.md — uses a hardcoded date instead of the {PR_MERGE_DATE} placeholder.

Important Files Changed

Filename	Overview
extensions/zod-documentation/CHANGELOG.md	New entry uses a hardcoded date (2026-05-22) instead of the required {PR_MERGE_DATE} placeholder.
extensions/zod-documentation/src/flatten-docs.ts	URL construction correctly hardcodes per-version base URLs; zodVersion is properly passed as a parameter rather than captured at module load time.
extensions/zod-documentation/src/search-documentation.tsx	Clean implementation of the Zod version dropdown and list; passes zodVersion as a parameter to flattenDocs correctly.
extensions/zod-documentation/package.json	Unused @raycast/utils dependency removed; only @raycast/api remains as a production dependency.
extensions/zod-documentation/eslint.config.js	Migrated from legacy .eslintrc.json to ESLint v9 flat config with correct defineConfig import from eslint/config.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
extensions/zod-documentation/CHANGELOG.md:3
The new changelog entry uses a hardcoded date instead of the `{PR_MERGE_DATE}` placeholder. Per the Raycast changelog convention, new entries should use `{PR_MERGE_DATE}`, which is automatically populated when the PR is merged.

```suggestion
## [Zod 4] - {PR_MERGE_DATE}
```

_{Reviews (3): Last reviewed commit: "Update CHANGELOG.md, add platforms field..." | Re-trigger Greptile}

[0xdhrv]

Looks good to me, approved ✅

[github-actions]

Published to the Raycast Store:
https://raycast.com/danieldeichfuss/zod-documentation

[raycastbot]

🎉 🎉 🎉

We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag.