Uh oh!
There was an error while loading. Please reload this page.
feat: upgrade existing sessions to v2 refresh tokens though config value - #2356
Merged
Conversation
hfforce-pushed
the
hf/upgrade-refresh-tokens-v2
branch
2 times, most recently
from
January 28, 2026 10:54
7607b3d to
f84f272Comparehfforce-pushed
the
hf/upgrade-refresh-tokens-v2
branch
from
January 28, 2026 11:17
f84f272 to
384f769CompareUh oh!
There was an error while loading. Please reload this page.
Pull Request Test Coverage Report for Build 21438517549Details
💛 - Coveralls |
fadymak
reviewed
Jan 28, 2026
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
fadymak
approved these changes
Jan 28, 2026
Uh oh!
There was an error while loading. Please reload this page.
cstockton pushed a commit
that referenced
this pull request
Jan 28, 2026
🤖 I have created a release *beep* *boop* --- ## [2.186.0](v2.185.0...v2.186.0) (2026-01-28) ### Features * Add email send operation metrics ([#2311](#2311)) ([0096575](0096575)) * add Supabase Auth identifier to OAuth redirect URLs ([#2299](#2299)) ([2d3dbc6](2d3dbc6)) * log sb-auth-user-id, sb-auth-session-id, ... on sign in not just refresh token ([#2342](#2342)) ([a486ada](a486ada)) * **oauth-server:** store and enforce token_endpoint_auth_method ([#2300](#2300)) ([bcd6cd5](bcd6cd5)) * replace JWT OAuth state with `flow_state.id` UUID ([#2331](#2331)) ([645654d](645654d)) * upgrade existing sessions to v2 refresh tokens though config value ([#2356](#2356)) ([6fb0e8a](6fb0e8a)) ### Bug Fixes * reloader unittest races on writeWg ([#2352](#2352)) ([088b714](088b714)) * update migration version ([#2343](#2343)) ([61ef4db](61ef4db)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: supabase-releaser[bot] <223506987+supabase-releaser[bot]@users.noreply.github.com>
hf added a commit
that referenced
this pull request
Feb 9, 2026
…st (#2371) In #2356 a session would be upgraded to v2 refresh tokens based on the number of requests for that session. If you set a percentage value of 10% and there's 100 refresh token requests per session, all sessions would be upgraded within 1 day. This is rectified here by converting the session ID to a value in the `[0, 100)` range making sure that a random selection of sessions would be upgraded consistently.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If the refresh token algorithm version is set to 2, only new sessions would be using these. By setting
GOTRUE_SECURITY_REFRESH_TOKEN_UPGRADE_PERCENTAGEto a value between 0 and 100 inclusive, on the next refresh token request a session using a v1 refresh token will switch to using a v2 refresh token.The percentage is to allow for gradual rollout, as the upgrade step can result in some concurrent refreshes to terminate the session early.