Update dependency @supabase/supabase-js to v2.103.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@supabase/supabase-js (source)	2.100.0 → 2.103.3

---

Release Notes

supabase/supabase-js (@​supabase/supabase-js)

v2.103.3

Compare Source

This was a version bump only for @​supabase/supabase-js to align it with other projects, there were no code changes.

v2.103.2

Compare Source

This was a version bump only for @​supabase/supabase-js to align it with other projects, there were no code changes.

v2.103.1

Compare Source

This was a version bump only for @​supabase/supabase-js to align it with other projects, there were no code changes.

v2.103.0

Compare Source

This was a version bump only for @​supabase/supabase-js to align it with other projects, there were no code changes.

v2.102.1

Compare Source

This was a version bump only for @​supabase/supabase-js to align it with other projects, there were no code changes.

v2.102.0

Compare Source

🚀 Features

• supabase: export PostgrestFilterBuilder and StorageApiError from supabase-js (#​2222)
• postgrest: add automatic retries for transient errors (#​2072)

❤️ Thank You

• Guilherme Souza
• Katerina Skroumpelou @​mandarini

v2.101.1

Compare Source

This was a version bump only for @​supabase/supabase-js to align it with other projects, there were no code changes.

v2.101.0

Compare Source

This was a version bump only for @​supabase/supabase-js to align it with other projects, there were no code changes.

v2.100.1

Compare Source

🩹 Fixes

• postgrest: narrow tstyche testFileMatch to only type test files (#​2193)

❤️ Thank You

• Katerina Skroumpelou @​mandarini

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[pubkey]

@copilot the CI for this fails, please inspect the logs and fix.

[Copilot]

@copilot the CI for this fails, please inspect the logs and fix.

The CI was failing due to a TypeScript type error in src/plugins/replication-supabase/index.ts. The new @supabase/supabase-js v2.103.3 has stricter and more deeply nested conditional types for the .eq() filter method, which caused TypeScript to fail with "Type instantiation is excessively deep and possibly infinite" when resolving the chain's return type.

Fixed in commit e1ff889 by casting options.client to any in the fetchById function, which bypasses the overly complex Supabase generic type recursion for that specific query chain.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[pubkey]

@copilot supabase sync test still fails:

12 passing (11s)
1 failing

1. replication-supabase.test.ts
   base test suite
   live replication
   two collections:
   Error: Timeout of 10000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/runner/work/rxdb/rxdb/test_tmp/replication-supabase.test.js)
   at listOnTimeout (node:internal/timers:605:17)
   at process.processTimers (node:internal/timers:541:7)

[Copilot]

@copilot supabase sync test still fails:

...

Fixed in commit cc6a027.

Root cause: RealtimeClient.channel() in realtime-js v2.100.0+ returns the existing channel when the same topic is requested, rather than creating a new one. When two collections share the same supabase client and tableName, the second call to .channel('realtime:humans') returns the already-joined channel from the first replication. Then .on('postgres_changes', ...) on an already-joined channel throws ("cannot add postgres_changes callbacks after subscribe()" - added in v2.101.0). This error propagates out of the monkey-patched start() before startBefore() is called, leaving startPromise unresolved and causing awaitInitialReplication() to hang indefinitely (10s mocha timeout).

Fix: use options.replicationIdentifier as the channel name (unique per replication instance) instead of the shared 'realtime:' + tableName. Also switched cleanup from sub.unsubscribe() to options.client.removeChannel(sub) for proper channel teardown.