Merge pull request #333 from supertokens/changelog-fix

fix: changelog

Author: rishabhpoddar

CHANGELOG.md

@@ -72,7 +72,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 -   Passwordless recipe changes:
     -   Added `tenantId` param to `ValidateEmailAddress`, `ValidatePhoneNumber` and `GetCustomUserInputCode` functions in `TypeInput`
     -   Added mandatory `TenantId` field to `emaildelivery.PasswordlessLoginType` and `smsdelivery.PasswordlessLoginType`
-    -   The providers array in `TypeInput` accepts `[]ProviderInput` instead of `[]TypeProvider`. TypeProvider interface is re-written. Refer migration section for more info.
     -   Added mandatory `tenantId` in the input to the following recipe index functions:
         -   `CreateCodeWithEmail`
         -   `CreateCodeWithPhoneNumber`
@@ -111,6 +110,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
         -   `EmailExistsGET`
         -   `PhoneNumberExistsGET`
 -   ThirdParty recipe changes
+    -   The providers array in `SignInUpFeature` accepts `[]ProviderInput` instead of `[]TypeProvider`. TypeProvider interface is re-written. Refer migration section for more info.
     -   Removed `SignInUp` and added `ManuallyCreateOrUpdateUser` instead in the recipe index functions.
     -   Added `ManuallyCreateOrUpdateUser` to recipe interface which is being called by the function mentioned above.
         -   `ManuallyCreateOrUpdateUser` recipe interface function should not be overridden as it is not going to be called by the SDK in the sign in/up flow.
@@ -220,7 +220,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
     }
     ```
 
--   Single instance with multiple clients of each provider instead of multiple instances of them. Also use `clientType` to differentiate them. `clientType` passed from the frontend will be used to determine the right config.
+-   Single instance with multiple clients of each provider instead of multiple instances of them. Also use `clientType` to differentiate them. `clientType` passed from the frontend will be used to determine the right config. `IsDefault` option has been removed and `clientType` is expected to be passed when there are more than one client. If there is only one client, `clientType` is optional and will be used by default.
 
     Before: