fix: remove jq from vercel script

[thebrianchen]

Pull Request Checklist

• Did you add new tests and confirm existing tests pass? (yarn test)
• Did you update relevant docs? (docs are found in the site folder, and guidelines for updating/adding docs can be found in the contribution guide)
• Do your commits follow the Conventional Commits standard?
• Does your PR title also follow the Conventional Commits standard?
• If you have a breaking change, is it correctly reflected in your commit message? (e.g. feat!: breaking change)
• Did you run lint (yarn lint:check) and fix any issues? (yarn lint:write)
• Did you follow the contribution guidelines?

---

PR-Codex overview

This PR updates the scripts/vercel-ignore-build.sh script to improve error handling when fetching pull request information from the GitHub API, replacing jq with grep and sed for compatibility with Vercel's environment.

Detailed summary

• Replaced jq with grep and sed to parse JSON response.
• Added error handling for empty responses and API errors.
• Extracted base.ref from the JSON response using grep and sed.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
aa-sdk-ui-demo	Ready	Preview	Comment	Sep 29, 2025 11:23pm

[github-actions]

🌿 Documentation Preview

Name	Status	Preview	Updated (UTC)
Alchemy Docs	✅ Ready	🔗 Visit Preview	Sep 29, 2025, 11:18 PM

[Copilot]

Pull Request Overview

This PR removes the dependency on jq from the Vercel build script by replacing JSON parsing with native shell utilities. The change addresses the issue that jq is not available in the Vercel build environment.

• Replaces jq JSON parsing with grep and sed commands
• Adds error handling for GitHub API responses
• Maintains the same functionality for extracting the PR base branch

[Copilot]

The regex pattern for extracting error messages is fragile and may break if the JSON contains escaped quotes or other special characters within the message string. Consider using a more robust approach or adding validation to handle edge cases.

Suggested change

	ERROR_MSG=$(echo "$PR_RESPONSE" | grep -o '"message":"[^"]*"' | sed 's/"message":"\([^"]*\)"/\1/')
	ERROR_MSG=$(echo "$PR_RESPONSE" | python3 -c 'import sys, json; print(json.load(sys.stdin).get("message", ""))')

[thebrianchen]

stick with grep/sed, since python env is much less certain and can change with version

[jakehobbs]

approved assuming you saw copilot's comment & aren't concerned