Skip to content

fix(version): reconcile supabase-js version drift to v2.110.8#1216

Merged
github-actions[bot] merged 1 commit into
Nightlyfrom
nightly/stage-7-version-integrity-2d8c54a9-4024414400849302396
Jul 25, 2026
Merged

fix(version): reconcile supabase-js version drift to v2.110.8#1216
github-actions[bot] merged 1 commit into
Nightlyfrom
nightly/stage-7-version-integrity-2d8c54a9-4024414400849302396

Conversation

@google-labs-jules

Copy link
Copy Markdown
Contributor

Generated by: .github/nightly-prompts/07-version-integrity.md

Reasoning:

[Discrepancy]: The central catalog in pnpm-workspace.yaml declares @supabase/supabase-js as ^2.110.8, but 7 Backend Supabase Edge Functions and the fetch_player_battles.ts utility script were importing v2.110.7.
[Rule Applied]: Catalog Alignment / Target A: Unitary Versioning.
[Rationale]: The monorepo requires absolute consistent package referencing to align with the central catalog, ensuring substrate stability and preventing version drift.

Changes:

  • [Backend Edge Functions]: Synchronized @supabase/supabase-js from 2.110.7 to 2.110.8 in ingest-royale-data, vault.ts, protocol.ts, sync-player-cards, query-royale-api, fetch-player-battlelog, and headhunter-scanner clients.
  • [GitHub Runner Scripts]: Synchronized @supabase/supabase-js from 2.110.7 to 2.110.8 in .github/scripts/fetch_player_battles.ts.

Verification:

  • [Automated]: Verified that pnpm test successfully executes with 1421 passing tests.
  • [Automated/Audit]: Verified monorepo version integrity via pnpm audit:version.

Log Updates:

  • Updated .github/nightly-logs/07-version-integrity-coverage.log
  • Updated .github/nightly-logs/00-pr-history.md

PR created automatically by Jules for task 4024414400849302396 started by @AlbiDR

Reconcile the @supabase/supabase-js dependency version across all
Backend Supabase Edge Functions and the fetch_player_battles.ts
utility script to match the updated pnpm-workspace.yaml catalog.
@google-labs-jules

Copy link
Copy Markdown
Contributor Author

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@supabase

supabase Bot commented Jul 25, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project hucktamloykszinwbtuh because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@github-actions
github-actions Bot merged commit ec759d4 into Nightly Jul 25, 2026
3 checks passed
@github-actions
github-actions Bot deleted the nightly/stage-7-version-integrity-2d8c54a9-4024414400849302396 branch July 25, 2026 04:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants