Engine versions
- Node:
14.21.3 - MongoDB:
4.4, 5.0, 6.0 - Apps-Engine:
1.40.0
Patch Changes
-
535ca09: Bump @rocket.chat/meteor version.
-
Bump @rocket.chat/meteor version.
-
b1f62c4: fix: wrong client hash calculation due to race condition on assets
Some deployments may suffer from some reloads if running multiple instances. It's caused by different client hashes generated due to a possible race condition on custom assets load at the startup time. Forcing the clients to talk to the right backend instances, which causes reloads if sticky sessions are not enabled.
This change removes the assets from the hash calculation preventing the race condition and possible different hashes. After this change, the clients will not reload when the admin changes assets. -
cc5530a: fix: immediate auto reload issues
Immediate auto reload increases server load on restarts/upgrades and increases the chance of getting 404 on Meteor's config file blocking the UI on a loading screen
This change adds delays on front and backend codes on automatic client reload:
- Front-end, adds a warning message including the old and new hashes, and a delay of 60 seconds after being notified by the server
- Back-end, delays the client notifications on a random value between 2 and 10 minutes per connection, allowing different clients to reload at different moments and distributing the load along the time.
- @rocket.chat/core-typings@6.3.11
- @rocket.chat/rest-typings@6.3.11
- @rocket.chat/api-client@0.1.11
- @rocket.chat/omnichannel-services@0.0.17
- @rocket.chat/pdf-worker@0.0.17
- @rocket.chat/presence@0.0.17
- @rocket.chat/core-services@0.1.11
- @rocket.chat/cron@0.0.13
- @rocket.chat/gazzodown@1.0.11
- @rocket.chat/model-typings@0.0.17
- @rocket.chat/ui-contexts@1.0.11
- @rocket.chat/fuselage-ui-kit@1.0.11
- @rocket.chat/models@0.0.17
- @rocket.chat/ui-theming@0.0.1
- @rocket.chat/ui-client@1.0.11
- @rocket.chat/ui-video-conf@1.0.11
- @rocket.chat/web-ui-registration@1.0.11
- @rocket.chat/instance-status@0.0.17