@everyone new version of core (v3.6.0) & backend SDKs released: Core's new feature: 1) Able to configure email verification and password reset token's lifetime via the core's config.yaml file / docker env vars. 2) Support for multiple access token signing keys so that there is no spike in the refresh API calls when an access token signing key has changed (performance optimisation) Backend SDKs: - Changes to work well with (2) from above. The changes in the backend SDK are non breaking. To move from an older version of the core to the current one, there are a few db schema changes: a) New table called

session_access_token_signing_keys

b) New table called

jwt_signing_keys

c) For users of postgresql, there is a change in the type of

user_id

column in the

emailverification_verified_emails

and

emailverification_tokens

tables -> from

varchar(255)

to

varchar(128)

The db schema changes should happen on their own when you start the new core version, except for change in (c). But that is not a necessary change to make 🙂