Rocket.Chat 8.3.7
Patch release with security hotfixes and permission enforcement improvements. Fixes user token generation permission checks and ensures consistent room permission validation when converting channels to teams.
Engine versions
- Node:
22.16.0 - Deno:
1.43.5 - MongoDB:
8.0 - Apps-Engine:
1.61.1
Patch Changes
-
Bump @rocket.chat/meteor version.
-
(#41237 by @dionisio-bot) Security Hotfix (https://docs.rocket.chat/docs/security-fixes-and-updates)
-
(#41246 by @dionisio-bot) Security Hotfix (https://docs.rocket.chat/docs/security-fixes-and-updates)
-
(#41295 by @dionisio-bot) Ensures the
users.CreateTokenendpoint checks for theuser-generate-access-tokenpermission when generating a login token for another user -
(#41280 by @dionisio-bot) Ensures room permission checks are applied consistently regardless of how the room is identified when converting a channel to a team or creating a team from an existing room
-
Updated dependencies [c15e433]:
- @rocket.chat/core-typings@8.3.7
- @rocket.chat/model-typings@2.1.7
- @rocket.chat/models@2.1.7
- @rocket.chat/rest-typings@8.3.7
Source: original entry ↗
More from Rocket.Chat
Follow Rocket.Chat to get its new changes in your feed and email digest.
8.9.0 LTS
Rocket.Chat 8.9.0 LTS introduces a realtime message composer, hybrid AI search with semantic and keyword retrieval, custom sidebar categories for enterprise users, improved video conferencing with dedicated call windows, new API endpoints for messages and call history, and enhanced draft handling. The release also deprecates Custom OAuth on non-Premium plans and Gravatar integration ahead of future major versions.
8.9.0-rc.5
Release candidate 8.9.0-rc.5 with engine version updates including Node >=22.22.3 or >=24.15.0, MongoDB 8.0, and Apps-Engine 1.67.0-rc.0. Includes dependency updates for core typings and REST typings packages.
Rocket.Chat 8.9.0-rc.4
Custom OAuth authentication will require a Premium license in version 9.0.0; workspaces without a Premium plan now see warnings in admin settings and logs. Audio and video attachments served through S3 or Google Cloud Storage proxy now support byte-range requests for proper duration display, seek functionality, and progress tracking.