chore(deps): bump @supabase/ssr from 0.12.0 to 0.12.3#950
Conversation
--- updated-dependencies: - dependency-name: "@supabase/ssr" dependency-version: 0.12.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
|
Warning Review limit reached
Next review available in: 23 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe pull request updates ChangesSupabase SSR Dependency Update
Client Bundle Secret Detection
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
CI triageCI failed on this PR. Automated classification of the 2 failed job(s):
Compared with main CI run #3907 (success). Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger. |
|
@coderabbitai Please can you resolve all of the failing CI testing for me and ensure no regression and fix everything for me. Please also resolve the failing Policy CI test as well if present |
|
✅ CI fix PR created: Follow
4 failing check(s)
1 file(s) modified
View agent analysis |
|
@claude resolve PR Policy CI failure |
|
@coderabbitai please resolve failing CI/Build testing |
…d application build requirements (#969) Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
|
@coderabbitai Please ensure that all CI testing is passing |
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
scripts/check-client-bundle-secrets.mjs (1)
54-58: 🎯 Functional Correctness | 🔵 Trivial | ⚡ Quick win
content.match()only captures the first match per file.Without the
gflag,String.prototype.match()returns only the first occurrence. If a file contains multiple distinct Supabase secrets, only the first is recorded as an offender. The build still fails, but a developer who fixes only the flagged secret will need another build cycle to discover the next one. Consider usingmatchAll(which requires thegflag on the regex) to surface all matches in a single pass.♻️ Proposed refactor: use matchAll for complete detection
Add the
gflag to the regex on line 18:- /\bsb_secret_[A-Za-z0-9_-]{20,}\b/, + /\bsb_secret_[A-Za-z0-9_-]{20,}\b/g,Then iterate all matches in the scanning logic:
- const matchedText = - marker instanceof RegExp ? content.match(marker)?.[0] : content.includes(marker) ? marker : null; - if (matchedText) { - const relativePath = relative(projectRoot, file).replaceAll("\\", "/"); - offenders.set(`${relativePath}\0${matchedText}`, { marker: matchedText, relativePath }); + const relativePath = relative(projectRoot, file).replaceAll("\\", "/"); + if (marker instanceof RegExp) { + for (const match of content.matchAll(marker)) { + offenders.set(`${relativePath}\0${match[0]}`, { marker: match[0], relativePath }); + } + } else if (content.includes(marker)) { + offenders.set(`${relativePath}\0${marker}`, { marker, relativePath }); }🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@scripts/check-client-bundle-secrets.mjs` around lines 54 - 58, Update the RegExp branch in the scanning logic around matchedText to collect every occurrence in each file, not only the first match. Ensure the configured marker regex is global for matchAll, iterate all matches, and add each matched value to offenders while preserving the existing literal-marker behavior and deduplication key.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@scripts/check-client-bundle-secrets.mjs`:
- Around line 54-58: Update the matched-secret handling in the marker scan and
offender reporting flow so regex matches retain the raw value only for internal
deduplication, while the stored/logged marker uses a masked or truncated
placeholder. Ensure CI output never includes the full matched value, including
when processing sb_secret_... regex detections.
---
Nitpick comments:
In `@scripts/check-client-bundle-secrets.mjs`:
- Around line 54-58: Update the RegExp branch in the scanning logic around
matchedText to collect every occurrence in each file, not only the first match.
Ensure the configured marker regex is global for matchAll, iterate all matches,
and add each matched value to offenders while preserving the existing
literal-marker behavior and deduplication key.
🪄 Autofix (Beta)
❌ Autofix failed (check again to retry)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 2ae0cff2-7313-44f6-a286-f3a4d388b3dc
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (2)
package.jsonscripts/check-client-bundle-secrets.mjs
🚧 Files skipped from review as they are similar to previous changes (1)
- package.json
|
Note Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it. The branch was updated while autofix was in progress. Please try again. |
1 participant
Summary
@supabase/ssrfrom0.12.0to0.12.3; affects the Supabase SSR integration and lockfile dependency resolution only.Verification
npm run verify:pr-localnpm run verify:uinot run: no UI, routing, styling, browser behavior, reduced-motion, or forced-colors behavior changednpm run verify:releasenot run: dependency patch update only; no release or handoff confidence claim in this PRnpm run eval:retrieval:qualitynot run: no retrieval, ranking, selection, chunking, or scoring behavior changednpm run eval:rag -- --limit 15+npm run eval:quality -- --rag-onlynot run: no answer generation, synthesis prompt, or answer post-processing behavior changednpm run check:production-readinessnot run: no clinical workflow, privacy, environment, Supabase target, source governance, or deployment behavior changed by this dependency bumpnpm run check:deployment-readinessnot run: no deployment startup, hosting, or rollout behavior changedRisk and rollout
@supabase/ssrwith no intended application behavior change beyond upstream fixes and compatibility improvements.@supabase/ssrto0.12.0and regenerate the lockfile from the reverted manifest.Clinical Governance Preflight
Clinical KB Database(sjrfecxgysukkwxsowpy)Notes
@supabase/ssrfrom0.12.0to0.12.3.Summary by CodeRabbit
Bug Fixes
Chores