You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
8
8
9
9
## [unreleased]
10
10
11
+
## [0.23.0] - 2024-06-24
12
+
13
+
### Breaking change
14
+
15
+
- The access token cookie expiry has been changed from 100 years to 1 year due to some browsers capping the maximum expiry at 400 days. No action is needed on your part.
16
+
11
17
## [0.22.1] - 2024-06-10
12
18
- Remove `user_context` being `None` check in querier delete function to make it consistent with other non GET functions
# We set the expiration to 100 years, because we can't really access the expiration of the refresh token everywhere we are setting it.
394
+
# We set the expiration to 1 year, because we can't really access the expiration of the refresh token everywhere we are setting it.
395
395
# This should be safe to do, since this is only the validity of the cookie (set here or on the frontend) but we check the expiration of the JWT anyway.
396
396
# Even if the token is expired the presence of the token indicates that the user could have a valid refresh
397
-
# Setting them to infinity would require special case handling on the frontend and just adding 10 years seems enough.
398
-
get_timestamp_ms() +HUNDRED_YEARS_IN_MS,
397
+
# Some browsers now cap the maximum expiry at 400 days, so we set it to 1 year, which should suffice.
0 commit comments