Skip to content

Comments

[pull] master from supabase:master#640

Merged
pull[bot] merged 4 commits intocode:masterfrom
supabase:master
Feb 2, 2026
Merged

[pull] master from supabase:master#640
pull[bot] merged 4 commits intocode:masterfrom
supabase:master

Conversation

@pull
Copy link

@pull pull bot commented Feb 2, 2026

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

jordienr and others added 4 commits February 2, 2026 10:46
- finished the axiom log drain started in #40209 

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

## Release Notes

* **New Features**
* Added Axiom as a new log drain destination for telemetry data
collection
  * Added Amazon S3 as a new log drain destination for log storage
* Extended log drain configuration form with fields for S3 bucket
credentials and Axiom API details
  * Added documentation for setting up Axiom log drain integration

* **Documentation**
* Added Axiom log drain setup guides with dataset creation and
configuration steps

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
… ID (#42386)

## Summary

Adds session-based deduplication for experiment exposure events.
Previously, exposure events used `useRef` which reset on page refresh,
causing duplicate events. Now events dedupe by PostHog session ID using
`sessionStorage`, firing once per session even across page refreshes.

## Changes

- Add `captureExperimentExposure()` method to `PostHogClient` with
session-based dedupe
- Add `getSessionId()` method to retrieve PostHog session ID
- Create `useTrackExperimentExposure` hook for clean usage
- Migrate existing experiments to new hook:
  - RLS option experiment (`/new/[slug]`)
  - Realtime button experiment
  - Table create generate policies experiment

## How it works

1. Event triggered → if PostHog not ready, queue to `pendingExposures[]`
2. PostHog `loaded` → flush queue through `fireExposureIfNew()`
3. `fireExposureIfNew()` checks
`sessionStorage['ph_exposed:{experimentId}']`
4. If value matches current session ID → skip (already fired)
5. If differs or missing → fire event, store session ID

## Testing

- [x] Tested locally and on preview - verified on project creation page
- [x] PostHog events sent successfully (200 responses)
- [x] Session deduplication working (no duplicate events on page refresh
or org switch)
- [x] Lint passes with 0 errors

**Quick test:**
1. Go to `/new/<org-slug>` project creation page
2. Check `sessionStorage` for `ph_exposed:project_creation_rls_option`
key
3. Refresh page - event should not fire again (same session ID)

## Linear

Resolves GROWTH-608

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **New Features**
* More reliable experiment exposure reporting with session-aware
deduplication, queued delivery, and consent respect to ensure events are
recorded when available.
* **Bug Fixes**
* Prevents duplicate exposure events within a session and avoids firing
exposures without a valid session.
* **Refactor**
* Consolidated disparate exposure-tracking logic into a unified
hook-based approach, simplifying tracking across the app.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Automated weekly decrease of ESLint ratchet baselines.

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
## I have read the
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
file.

YES

## What kind of change does this PR introduce?
Update OG image for the PrivateLink blog post

## What is the current behavior?
Old OG image

## What is the new behavior?
Updated OG image

## Additional context
Follow-up to #42178 - updating the OG image for the PrivateLink
announcement blog post.

Co-authored-by: Ana Mogul <ana1337x@users.noreply.github.com>
@pull pull bot locked and limited conversation to collaborators Feb 2, 2026
@pull pull bot added the ⤵️ pull label Feb 2, 2026
@pull pull bot merged commit adf7d06 into code:master Feb 2, 2026
@github-actions github-actions bot added the documentation Improvements or additions to documentation label Feb 2, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

⤵️ pull documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants