Fix Google Chrome history search when Chrome is running

[Jeffrey95]

Description

Bumps @raycast/utils from ^2.2.2 to ^2.2.4 to pick up the useSQL lock fallback fix for node:sqlite.

When Chrome is running, searching Chrome history can fail with database is locked. The extension already uses useSQL, which has a fallback that copies the database to a temporary file when SQLite reports the source DB is locked. However, older @raycast/utils versions only detected lock errors from message text like (5)/(14). With Raycast's newer Node runtime, node:sqlite reports the lock as errcode: 5 with message database is locked, so the fallback was not triggered.

This matches the root cause fixed for Zen Browser in #27373. Updating @raycast/utils makes useSQL detect the node:sqlite error code and use the existing DB-copy fallback.

Fixes #27493

Verification

• Reproduced the failure locally with @raycast/utils 2.2.2 while Chrome was running.
• Verified that the same extension works after bumping to @raycast/utils 2.2.4.
• Ran npx tsc --noEmit.
• Ran npm run lint.
• Ran npm run build.

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 first contribution! 🎉

🔔 @rgomezcasas @bromanko @crisboarna @andreaselia @rtyke @karolre @Aiee @nagauta @a-laughlin @tleo19 @Tarocch1 @rsperezn @drewbabel @haydencbarnes @pernielsentikaer @j3lte @0xdhrv @xmok @hayk94 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="fix/google-chrome-utils-lock-fallback"
FORK_URL="https://github.com/Jeffrey95/extensions.git"
EXTENSION_NAME="google-chrome"
REPO_NAME="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 bumps @raycast/utils from ^2.2.2 to ^2.2.4 to pick up the useSQL lock-fallback fix, which makes Chrome history search work correctly when Chrome is running and holding the SQLite database locked.

• package.json / package-lock.json: version bump to @raycast/utils 2.2.4; no other dependency changes.
• CHANGELOG.md: new entry added at the top of the file documenting the fix.

Confidence Score: 5/5

Safe to merge — the change is a targeted patch-version dependency bump with a well-understood, previously verified fix.

The only substantive change is upgrading @raycast/utils by two patch versions to restore the database-lock fallback path. The lock file update is consistent with the version change and the peer: true flag additions are an expected npm lockfile v3 artefact. The sole nit is the hardcoded date in CHANGELOG.md instead of the {PR_MERGE_DATE} placeholder.

No files require special attention.

Important Files Changed

Filename	Overview
extensions/google-chrome/CHANGELOG.md	New entry added at the top; uses a hardcoded date instead of the required {PR_MERGE_DATE} placeholder.
extensions/google-chrome/package.json	Bumps @raycast/utils from ^2.2.2 to ^2.2.4 to pick up the useSQL lock-fallback fix.
extensions/google-chrome/package-lock.json	Lock file updated for @raycast/utils 2.2.4; several peer-dependency entries gained the "peer: true" flag, consistent with an npm lockfile v3 refresh.

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/google-chrome/CHANGELOG.md:3
The new changelog entry uses a hardcoded date (`2026-05-07`) instead of the `{PR_MERGE_DATE}` placeholder. The Raycast repository convention is to leave `{PR_MERGE_DATE}` as-is so the release tooling substitutes the actual merge date automatically.

```suggestion
## [Fix Chrome History Search When Chrome Is Running] - {PR_MERGE_DATE}
```

_{Reviews (2): Last reviewed commit: "Update CHANGELOG.md" | Re-trigger Greptile}

[0xdhrv]

Looks good to me, approved ✅

[github-actions]

Published to the Raycast Store:
https://raycast.com/Codely/google-chrome

[raycastbot]

🎉 🎉 🎉

Such a great contribution deserves a reward, but unfortunately we couldn't find your Raycast account based on your GitHub username (@Jeffrey95).

Please link your GitHub account to your Raycast account to receive your credits and soon be able to exchange them for some swag.