An unexpected error occurred: Failed to match changelog: ## vNext (TBD) > [!NOTE] > This version communicates with Atlas Device Services through a different URL (https://services.cloud.mongodb.com). While we consider this an internal detail of the SDK, you might need to update rules in firewalls or other configuration that you've used to limit connections made by your app. ### Deprecations * None ### Enhancements * None ### Fixed * Fixed an endless loop of requests that would happen if linking credentials failed due to an authentication failure. ([#6588](https://github.com/realm/realm-js/pull/6588), since v0.6.0) * Logging in with `Credentials.anonymous()` credentials will now reuse any existing anonymous user which is already authenticated with the app. This aligns with the behaviour of the `realm` package and will result in less users being created. Use `Credentials.anonymous(false)` to disable this behaviour and achieve the old behaviour of creating new anonymous users on every login. ([#6592](https://github.com/realm/realm-js/pull/6592)) * Fixed crash in Chrome from calling `stream.return()` on a watch stream. (PR [#6688](https://github.com/realm/realm-js/pull/6688)) ### Internal * The base URL used to communicate with the Atlas App Services was changed from "https://realm.mongodb.com" to "https://services.cloud.mongodb.com". ([#6591](https://github.com/realm/realm-js/pull/6591)) * Avoid falling back to `_stitch_` prefixed values when parsing the querystring response from an OAuth2 redirection. ([#6659](https://github.com/realm/realm-js/pull/6659)) 2.0.0 Release notes (2022-10-18) ============================================================= ### Breaking Changes * `Realm.Credentials#google` with `authCode` parameter (use `authObject`) * The following should be replaced with `Realm.Credentials#apiKey`: * `Realm.Credentials#serverApiKey` * `Realm.Credentials#userApiKey` * The overload of `Realm.Auth.EmailPasswordAuth` methods, taking positional arguments instead of object arguments: * `registerUser` * `confirmUser` * `resendConfirmationEmail` * `retryCustomConfirmation` * `resetPassword` * `sendResetPasswordEmail` * `callResetPasswordFunction` Now the only supported call signature of `Realm.Auth.EmailPasswordAuth` methods is using a single object argument: ```typescript registerUser({ email, password }); confirmUser({ token, tokenId }); resendConfirmationEmail({ email }); retryCustomConfirmation({ email }); resetPassword({ token, tokenId, password }); sendResetPasswordEmail({ email }); callResetPasswordFunction({ email, password }, ...args); ``` ### Enhancements * None ### Fixed * None ### Internal * None 1.7.1 Release notes (2022-07-04) ============================================================= ### Breaking Changes * None ### Enhancements * None ### Fixed * Fixed an issue where closing a watch stream, by calling `return` on the `AsyncIterator`, wouldn't propagate to closing the underlying network connection. ([#4700](https://github.com/realm/realm-js/pull/4700)) ### Internal * None 1.7.0 Release notes (2022-02-14) ============================================================= ### Breaking Changes * None ### Enhancements * Added `Realm.App#deleteUser()` to delete a sync user from a MongoDB Realm app. ([#4006](https://github.com/realm/realm-js/issues/4006)) ### Fixed * None ### Internal * Updated base URL to https://realm.mongodb.com. ([#4283](https://github.com/realm/realm-js/pull/4283)) 1.6.0 Release notes (2022-01-26) ============================================================= ### Breaking Changes * None ### Enhancements * Adding support for passing the `arrayFilters` parameter when updating documents using the remote MongoDB client. ([#4248](https://github.com/realm/realm-js/pull/4248)) ### Fixed * None ### Internal * None 1.5.1 Release notes (2021-11-17) ============================================================= ### Breaking Changes * None ### Enhancements * None ### Fixed * Using `globalThis` instead of `window` global. This fix runti