chore: refresh frontend dependencies - #2
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 84ca9185df
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - run: npm ci | ||
| - run: npm run lint | ||
| - run: npm run validate-regions | ||
| - run: npm run build |
There was a problem hiding this comment.
The new workflow finishes after the build without executing node --test; package.json also defines no test script, and a repo-wide search found no other invocation. Consequently, tests/api-key-storage.test.mjs is never exercised automatically, so a pull request can regress the API-key storage guarantee while all CI checks remain green.
Useful? React with 👍 / 👎.
1 participant
What changed
Refreshes the locked frontend dependency tree and regenerates the tracked Vite production assets.
Why
The lockfile updates bring transitive frontend packages to their current compatible releases; the repository tracks its published
dist/output, so it is regenerated from the verified build.Validation
npm cinpm run lintnpm run buildnpm audit --omit=dev --audit-level=high(0 vulnerabilities)