chore: stop tracking compiled JS output; fix deploy pipeline trigger

[Copilot]

Compiled js/ artifacts were committed to the repo, causing repeated merge conflicts across concurrent PRs. Since deploy.yml already runs npm run build before staging files, the committed output was purely redundant.

Changes

• .gitignore — Replaced three granular patterns (js/*.js, js/*.js.map, js/*.d.ts) with a single js/ exclusion. The old patterns also missed *.d.ts.map files, which were being tracked.
• git rm --cached — Evicted the four already-tracked files (app.js, storage.js, app.d.ts.map, storage.d.ts.map) from the index without touching the working tree.
• update-cache-version.yml — Swapped the path trigger from js/** → src/** so the service-worker update → deploy chain still fires on TypeScript source changes now that js/ is no longer committed.

# before
paths:
  - 'js/**'

# after
paths:
  - 'src/**'

Original prompt

The .map files keep causing conflicts when I have multiple PRs open and the .js is redundant. My app is published with GitHub Pages and uses the #file:deploy.yml Is there a way to compile the ts files and make sure the .js files are available in prod?

The user has attached the following file paths as relevant context:

• .github\workflows\deploy.yml

Created from VS Code.

---

⚡ Quickly spin up Copilot coding agent tasks from anywhere on your macOS or Windows machine with Raycast.