v0.5.0: Introducing keys! (+migration checklist) #314
pilcrowonpaper
announced in
Announcements
Replies: 1 comment
-
Also, this should be the last update to the database model before 1.0. There likely will be changes to the API but it won't be something drastic, I think. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm excited to announce version 0.5.0!
The biggest change is the introduction of keys. Keys are similar to the provider id in the previous versions but it's now decoupled to user, allowing you to link multiple providers to a single user.
Migration
Update your packages
Every single package has a new version!
Update your database
key
tableprovider_id
,hashed_password
fromuser
tableexpires
column toactive_expires
insession
tableRefer to this guide for details.
Update APIs
getUserByProviderId()
:getKeyUser()
authenticateUser()
:validateKeyPassword()
updateUserPassword()
:updateKeyPassword()
updateUserProviderId
createUser()
: docsUpdate configuration
By default, Lucia will now generate its own user id. Add
generateCustomUserId()
if you want to let the database handle it (previous default behavior):Astro and SvelteKit integration packages
The
signOut()
function has been removed. Follow the following guides to implement sign out:0.6.0
Minor update: #324
Beta Was this translation helpful? Give feedback.
All reactions