Release 2.4.1

Breaking changes

• None

Bugs fixed

• 'ros start' now works again. (Regression was introduced in 2.4.0)

Enhancements

• None

Release 2.4.0

Breaking changes

• None

Bugs fixed

• Fixed an issue that allowed non-admin users to create Realms in other users'
  home folders.
• Fixed a bug causing the failover logic in SyncProxyService to trigger for
  no good reason. This would manifest itself in "End of input" error messages
  on the client in enterprise/cloud deployments.

Enhancements

• Added server.ensureRealmExists API to create a Realm if it doesn't exist
  already.

Release 2.3.0

Breaking changes

• None

Bugs fixed

• None

Enhancements

• Indicate the version of ROS using X-Powered-By Header.
• Added Server.applyPermissions method to allow changing permissions without
  having to log in with an admin user.

Release 2.2.0

Breaking changes

• None

Bugs fixed

• Export the JWT provider

Enhancements

• Export stats classes and interfaces

Release 2.1.1

Bugs fixed

• Fixed an import statement to make it work on case-sensitive file systems (Linux).
• Fixed a bug rendering ros backup useless because of incomplete path resolution for realm-backup.

Enhancements

• None

Release 2.1.0

Bugs fixed

• The LogService will now respect token revocations
• Revoked tokens will now never be assigned to the req.authToken.

Enhancements

• TypeScript and JavaScript templates now have .gitignore.
• The manual backup command is now available as ros backup.

Release 2.0.23

Bugs fixed

• None

Enhancements

• Added JWT authentication provider. It allows you to create a custom
  authentication service that issues signed Json Web Tokens that contain a
  userId and optional isAdmin fields. The app then transmits the token to
  ROS which verifies the signature and authenticates a user with the provided
  userId.

Release 2.0.22

Bugs fixed

• The health service no longer responds with 200 OK unless the server has fully
  started. It is 503 in case the server is still loading.
• The admin token user can now apply permission changes successfully.
• The early log messages do not get skipped in Studio any more.
• Users now have read-write access to their /~/__permission realms (again).
  The recent switch to read-only was an unintended breaking change.
• Fixed a potential race in the permission service. It reported itself started
  before setting up all the listeners and granting default permissions.
• [Object Server] Fixed a bug where deleted-then-recreated objects with identical
  primary keys become empty.
• [Object Server] Fixed a bug in outward partial sync to ensure
  convergence of partial sync in the case where the client creates a primary key object, that is already present on the server, and subscribes to it in the same transaction.
• Added error handling to the internal requests to the load balancer. This
  should fix some unhandled promise rejections.

Enhancements

• TypeScript and JavaScript templates now have .gitignore

Release 2.0.21

Bugs fixed

• Close all Permission Realm files used to avoid running out of file handles.

Enhancements

• None

Release 2.0.18

Breaking changes

• None

Bugs fixed

• Realms with invalid paths are now rejected. Previously ROS would reject those realms after creating metadata for them.
• Realms with invalid paths are now skipped during 1-to-2 migration. This is
  required because ROS-1 has the same behavior creating unsyncable realms, which
  we are not going to fix.
• Non-existent data files are not copied during 1-to-2 migration.
• The default port for BasicServer's https is now properly set to 9443
• HTTPS key and cert are now validated before attempting to start
• server.shutdown() is now more forgiving in failed state scenarios

Enhancements

• Server now has a simple method called openRealm that takes a remote path, like /__admin for example. This is always opened up with the internal server admin user. The schema is optional.