Skip to content

🔄 Sync with upstream changes#17

Open
h0lybyte wants to merge 420 commits into
mainfrom
upstream-main
Open

🔄 Sync with upstream changes#17
h0lybyte wants to merge 420 commits into
mainfrom
upstream-main

Conversation

@h0lybyte
Copy link
Copy Markdown
Member

Upstream Sync

This PR contains the latest changes from the upstream repository.

Changes included:

  • Synced from upstream/main
  • Auto-generated by upstream sync workflow

Review checklist:

  • Review the changes for any breaking changes
  • Check for conflicts with local modifications
  • Verify tests pass (if applicable)

This PR was automatically created by the upstream sync workflow

filipecabaco and others added 30 commits February 8, 2026 10:17
* feat: add per-client rate limiting for presence events

Adds rate limiting at the individual WebSocket connection level to prevent
a single client from exhausting the tenant's presence quota. Each client
is limited to a configurable number of presence calls within a time window
(defaults to 10 calls per 60 seconds).

new CLIENT_PRESENCE_MAX_CALLS and CLIENT_PRESENCE_WINDOW_MS options

This feature prevents individual misbehaving or malicious clients from consuming
the entire tenant's presence rate limit quota, improving
  fairness and abuse prevention.

* chore: add realtime channel tests

* fix: log new error message
In certain scenarios we end up with a difference between our metrics and the users metrics when it comes to migrations so this will self correct by checking the real count the user has in their database and we update our records
…e#1715)

* Increasing test coverage of overall code
* Reduce flakiness on certain tests
* Simplified and removed some hardcoded variables
* Partition CI for tests
* Properly cache docker images
* Cleanup actions and user blacksmith runners
Push Prometheus data to an endpoint periodically. An auth header can be specified
and it can conditionally compress (defaults to compress)
To improve operations we are going to separate tenant metrics from node metrics so we also separate product bound from operational bound workflows
semantic-release-bot and others added 30 commits May 18, 2026 21:30
* chore: action hardening

Removes interpolation and uses env instead. General hardening and best practice. Not reachable by untrusted code (forks/PRs)

* chore: more hard
We had the replay test failing more often than expected due to racing conditions between our tests and the inserts in the database which lead to a higher failure rate.

This also reduces the log noise to be more single line focused instead of tables and more noise that it's not useful for the e2e usecase
…base#1864)

This new endpoint sends a single broadcast with a JSON or binary payload

The content-type declares what kind of payload is being sent
* chore: reduce e2e flakiness

* chore: update nix node_modules hash

---------

Co-authored-by: supabase-autofix-bot <noreply@supabase.com>
…e#1903)

When `exp` and `iat` claims contain decimal number, channels close.
This commit fixes that by rounding the numbers to integer.

Closes supabase#1315.
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.

10 participants