All Versions
49
Latest Version
Avg Release Cycle
18 days
Latest Release
87 days ago
Changelog History
Page 1
Changelog History
Page 1
-
v4.2.0 Changes
November 07, 2022- ⚡️ Update dependencies for security updates: https://github.com/supertokens/supertokens-core/issues/525
-
v4.1.1 Changes
October 13, 2022- ⚡️ Updates core routes to now allow for trailing slashes
-
v4.1.0 Changes
September 22, 2022- ➕ Adds request IP allow & deny list: https://github.com/supertokens/supertokens-core/issues/511
-
v4.0.1 Changes
September 19, 2022- 🛠 Fixes bug related to implementationDependencies.json
-
v4.0.0 Changes
September 19, 2022➕ Added
- EmailPassword User migration API which allows you to import users with their email and password hashes.
- 👌 Support to import users with password hashes from Firebase
- 👌 Support with CDI version
2.16
- Hello API on
/
route.
Database Changes
- Updates the
password_hash
column in theemailpassword_users
table fromVARCHAR(128)
toVARCHAR(256)
to support more password hash lengths. Updates the
third_party_user_id
column in thethirdparty_users
table fromVARCHAR(128)
toVARCHAR(256)
to resolve https://github.com/supertokens/supertokens-core/issues/306⚡️ For legacy users who are self hosting the SuperTokens core run the following command to update your database with the changes:
- With MySql:
ALTER TABLE thirdparty_users MODIFY third_party_user_id VARCHAR(256); ALTER TABLE emailpassword_users MODIFY password_hash VARCHAR(256);
- With PostgreSQL:
ALTER TABLE thirdparty_users ALTER COLUMN third_party_user_id TYPE VARCHAR(256); ALTER TABLE emailpassword_users ALTER COLUMN password_hash TYPE VARCHAR(256);
- With MySql:
-
v3.16.2 Changes
September 02, 2022🐛 Bug fixes
- ⚡️ Updated java-jwt to handle
null
claims in JWTs
- ⚡️ Updated java-jwt to handle
-
v3.16.1 Changes
September 02, 2022🐛 Bug fixes
- 🛠 Fixed handling of
null
in access token payloads: https://github.com/supertokens/supertokens-core/issues/499
- 🛠 Fixed handling of
-
v3.16.0 Changes
August 18, 2022- 🔄 Changes logging level of API start / finished & Cronjob start / finished to be
INFO
level instead ofDEBUG
level. - ➕ Added new config
log_level
to set logging level. Possible values areDEBUG
|INFO
|WARN
|ERROR
|NONE
. As an example, setting the log level toWARN
would make the core print outWARN
andERROR
level logs.
- 🔄 Changes logging level of API start / finished & Cronjob start / finished to be
-
v3.15.1 Changes
August 10, 2022- ⚡️ Updates UserIdMapping recipe to resolve UserId Mappings for Auth recipes in the core itself
-
v3.15.0 Changes
July 25, 2022- ➕ Adds UserIdMapping recipe
- 👌 Support for collecting and displaying failing tests
Database changes
- ➕ Adds
userid_mapping
table