adding dev-v0.23.0 tag to this commit to ensure building

Author: rishabhpoddar

html/supertokens_python/constants.html

@@ -42,7 +42,7 @@ <h1 class="title">Module <code>supertokens_python.constants</code></h1>
 from __future__ import annotations
 
 SUPPORTED_CDI_VERSIONS = [&#34;3.0&#34;]
-VERSION = &#34;0.22.1&#34;
+VERSION = &#34;0.23.0&#34;
 TELEMETRY = &#34;/telemetry&#34;
 USER_COUNT = &#34;/users/count&#34;
 USER_DELETE = &#34;/user/remove&#34;
@@ -56,7 +56,7 @@ <h1 class="title">Module <code>supertokens_python.constants</code></h1>
 API_VERSION = &#34;/apiversion&#34;
 API_VERSION_HEADER = &#34;cdi-version&#34;
 DASHBOARD_VERSION = &#34;0.7&#34;
-HUNDRED_YEARS_IN_MS = 3153600000000
+ONE_YEAR_IN_MS = 31536000000
 RATE_LIMIT_STATUS_CODE = 429</code></pre>
 </details>
 </section>

html/supertokens_python/recipe/session/cookie_and_header.html

@@ -65,7 +65,7 @@ <h1 class="title">Module <code>supertokens_python.recipe.session.cookie_and_head
     available_token_transfer_methods,
 )
 from ...logger import log_debug_message
-from supertokens_python.constants import HUNDRED_YEARS_IN_MS
+from supertokens_python.constants import ONE_YEAR_IN_MS
 
 if TYPE_CHECKING:
     from supertokens_python.framework.request import BaseRequest
@@ -419,11 +419,11 @@ <h1 class="title">Module <code>supertokens_python.recipe.session.cookie_and_head
         config,
         &#34;access&#34;,
         access_token,
-        # We set the expiration to 100 years, because we can&#39;t really access the expiration of the refresh token everywhere we are setting it.
+        # We set the expiration to 1 year, because we can&#39;t really access the expiration of the refresh token everywhere we are setting it.
         # 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.
         # Even if the token is expired the presence of the token indicates that the user could have a valid refresh
-        # Setting them to infinity would require special case handling on the frontend and just adding 10 years seems enough.
-        get_timestamp_ms() + HUNDRED_YEARS_IN_MS,
+        # Some browsers now cap the maximum expiry at 400 days, so we set it to 1 year, which should suffice.
+        get_timestamp_ms() + ONE_YEAR_IN_MS,
         transfer_method,
         request,
         user_context,
@@ -438,7 +438,7 @@ <h1 class="title">Module <code>supertokens_python.recipe.session.cookie_and_head
             config,
             &#34;access&#34;,
             access_token,
-            get_timestamp_ms() + HUNDRED_YEARS_IN_MS,
+            get_timestamp_ms() + ONE_YEAR_IN_MS,
             &#34;header&#34;,
             request,
             user_context,