2.2.0

Added

• Added support for Microsoft OAuth sign in
• Added deleteSocialAccount mutation, for deleting password-less accounts. Throws an error if run on an account with a password (#110)

Fixed

• Fixed issue with accounts not automatically activating (#114, thanks @Stalex89!)
• Fixed issue with plugin's field restrictions not applying to public schema (#109, thanks @Zsavajji!)

2.1.2

Fixed

• Fixed issue with mutation field validation throwing an error (#103)
• Fixed issue with social registration not marking users as active if skip activation is enabled (#100)

2.1.1

Misc

• Ensure Twitter OAuth credentials are removed from session

2.1.0

Added

• Added setting to skip user activation when registering through social mutations (#100)

Changed

• firstName and lastName have been migrated to fullName across all register and viewer mutations (#101)

Fixed

• Fixed updateViewer mutation not updating user's name (use fullName parameter, as above) (#101)
• Fixed deleteAccount mutation not deleting user (#102)

2.0.0

Added

• Added Craft 4 support! (#94) – huge thanks to Brandon Kelly for the PR!
• Added deleteAccount mutation (#84)

Changed

• PHP >8.0 is now required
• Craft >4.0 is now required
• The email verification email is now sent out to users when updating their email via the updateViewer mutation (#90)
• When using the JWT returned from a register mutation to authenticate requests, all requests will throw a Please activate your account error until the account is activated (#83)

Fixed

• When users register through a social mutation, they now receive an appropriate activation email (if enabled), rather than the set password email (#72)

1.12.3

Fixed

• Fixed issue with some custom fields breaking user registration mutations

1.12.2

Changed

• The password reset required flag is now respected. When a user with this flag set tries to authenticate, a password reset email is sent and an error message is returned (#81, thanks @nstCactus!)

Fixed

• Fixed migration issue that occurred when setting a password for users with an unverified email (created in the control panel) (#79, thanks @nstCactus!)
• Fixed compatibility issue with Craft 3.7.24 (#85)
• Fixed issue with contextual error messages not being returned (#74)
• Fixed issue with field permissions not always being applied properly

1.12.1

Fixed

• Fixed migration issue that occurred when not using multiple schemas (#78)

1.12.0

Added

• A TokenService::parseToken(string $jwt):Token method that allows parsing a JWT from anywhere, not just the Authorization HTTP header (#75, thanks @nstCactus!)
• The ability to pass the token as a string to the TokenService::getUserFromToken() method instead of always getting the token from the Authorization HTTP header (#75, thanks @nstCactus!)

Changed

• Tokens now store schema references via schemaName instead of schemaId to improve cross-environment behaviour (#64, thanks @SayChi!)
• Creating new entries via a mutation no longer forces the author to be the current user, if an authorId argument is supplied (note: it still respects the Restricted Entry Mutations plugin settings!) (#63, thanks @cliveportman!)

Fixed

• Fixed issue with user mutation fields not clearing value if sent as null (#73, thanks @hendrik-agprop!)
• Fixed issue with users not being created as pending if 'suspend users by default' was enabled (#77, thanks @Zsavajji!)
• Fixed issue with authentication mutations returning Internal server error instead of contextual errors (#74)

1.11.5

Fixed

• Fixed issue with errors being thrown as Something went wrong when processing the GraphQL query. instead of contextual errors. E.g. requests with an expired token will now throw Invalid Authorization Header