Releases: RocketChat/Rocket.Chat
6.2.2
2023-05-19 · 1 🐛 · 2 👩💻👨💻
Engine versions
- Node:
14.21.3 - NPM:
6.14.17 - MongoDB:
4.4, 5.0, 6.0 - Apps-Engine:
1.39.1
🐛 Bug fixes
-
Livechat
CSPwhitelist validation (#29278)This PR fixes the Livechat CSP validation, which was incorrectly blocking access to the widget for all non whitelisted domains.
👩💻 👨💻 Core Team 🤓
6.2.1
2023-05-17 · 1 🔍 · 1 👩💻👨💻
Engine versions
- Node:
14.21.3 - NPM:
6.14.17 - MongoDB:
4.4, 5.0, 6.0 - Apps-Engine:
1.39.1
🔍 Minor changes
- Bump apps engine and vm2 (#29262)
👩💻 👨💻 Core Team 🤓
6.1.8
2023-05-17 · 1 🔍 · 1 👩💻👨💻
Engine versions
- Node:
14.21.2 - NPM:
6.14.17 - MongoDB:
4.4, 5.0, 6.0 - Apps-Engine:
1.38.4
🔍 Minor changes
- Bump apps engine and vm2 (#29260)
👩💻 👨💻 Core Team 🤓
6.0.8
2023-05-17 · 1 🔍 · 1 👩💻👨💻
Engine versions
- Node:
14.21.2 - NPM:
6.14.17 - MongoDB:
4.4, 5.0, 6.0
🔍 Minor changes
- Bump apps engine version and vm2 (#29259)
👩💻 👨💻 Core Team 🤓
5.4.10
2023-05-17 · 1 🔍 · 1 👩💻👨💻
Engine versions
- Node:
14.19.3 - NPM:
6.14.17 - MongoDB:
4.2, 4.4, 5.0
🔍 Minor changes
- Bump apps engine and vm2 (#29257)
👩💻 👨💻 Core Team 🤓
6.2.0
2023-05-15 · 9 🎉 · 2 🚀 · 80 🐛 · 290 🔍 · 56 👩💻👨💻
Engine versions
- Node:
14.21.3 - NPM:
6.14.17 - MongoDB:
4.4, 5.0, 6.0 - Apps-Engine:
1.39.0
🎉 New features
-
auto link custom domain (#28501)
Changes:
-
Auto Link Custom Domain new setting under Message group path:
/admin/settings/Message -
New translation keys for English
-
Adding types to message-parser
Options -
New hook
useAutoLinkDomainsto get the setting and return an array of domains
Desirable:
Output when the setting has the value:local,intranet -
-
Custom roles and Public&Private apps stats (#27781)
-
Make the marketplace search bar placeholder dynamic (#28394)
Jira task: AECO-24
Now the placeholder of the marketplace search bar will change based on which page of marketplace the user is browsing.
Demo gif:

-
Message Forwarding (#26662)
Implement the ability to forward messages to another channel, thread, or discussion. This is a high demand capability that is currently missing in Rocket.Chat. It can significantly improve the user's experience and her/his productivity. The scope of this project will be limited to the web application (not for mobile apps).
Special thanks to @nishant23122000 that helped us with this during GSOC 2022
-
moderation dashboard (#28962)
Release PR for the
feat/moderation-dashboardimplementing the Beta version of the Moderation Console. For more details & some previews on Moderation Console, read here -> #27961 (comment) -
New timeout setting for Omnichannel Webhooks (#28219 by @cauefcr)
Costumers were complaining about duplicated data from the Omnichannel webhooks, so I added a new setting that controls the timeouts for the webhooks, in the omnichannel->webhooks panel, the default values are 5s for http timeout, and 4x that for the retry timeout, or 20s.
-
Registered Loom oEmbed (#28339 by @Nabhag8848)
- Registered Loom OEmbed, Now Loom video links will show the embedded representation of URL shared like youtube and will have the better user experience for the teams using loom.
-
VideoConference Guest mode and Conference Router (#28186)
Jira Issue: [VC-79]
🚀 Improvements
-
Adding input type=password to AWS secrets fields (#28159)
Some fields that store secrets for AWS were exposing sensitive data because they didn't have the input type as
password.The change includes adding the password type and also changing the autocomplete value from
<PasswordInput />component to add the valuenew-passwordto avoid the browser autocompleting with the existing password. (This does not prevent the browser to show the hint to add the password) -
Galician onboarding translation (#27908 by @Thiagof99)
I've translated the entire onboarding page and forms to galician language. Here's an example of how the forms look now:

🐛 Bug fixes
-
#28762 - fix missing command in /help (#28777 by @adarshlilha)
When using
/helpcommand in any room the rocket.cat bot lists all keyboard shortcuts for the operations that can be done in rocket chat but for one command(marking all messages as read) shortcut is not being renderered -
ComposerPopupPreviewtrespassing the composer limit (#28896)before
after
-
emojiproperty in messages not being respected (#28416)There's a property on the message object called
emojiwhich allow the sender (bot, app, API, integration, etc) to replace the user avatar with an emoji. Since we rewrote the messages to React, this was not being supported.

-
UI_Use_Real_Namenot being respected in quotes and RoomForeword (#28613)Updated pertinent places and made it so user
nameis always sent with message (empty if non-existant). -
Add function to get installation source (#28806)
There have been reports of problems regarding the missing information of
installationSourcein apps. The only scenario where this information could be missing is if migrations failed to run properly when upgrading to 6.0. We haven't been able to identify the root cause yet, so we decided to provide a workaround in the meanwhile -
App crashing when switching to Hindi (hi-In) language (#28285 by @bhardwajdisha)
-
app status inconsistencies when running multiple instances in a cluster (#29180)
App status inconsistencies between multiple instances in a cluster boil down to the fact that the Apps-Engine is currently responsible for orchestrating when these events are triggered and is overly verbose in doing so.
Upon analysis, the framework itself should not have the concept of "other instances" - this is a deployment detail of the host system, and as such should be controlled by the host. The correct solution for this problem is to review this notification system, potentially removing it from the framework and leaving the responsibility solely for Rocket.Chat.
However, this is hindering the current app management experience for workspaces, so this PR cuts the control of some notifications that come from the framework (the more problematic ones) and moves the control over to RC in a short and practical way.
This is done by turning the methods of the most problematic events in the
AppActivationBridgeinto no-ops, and instead triggering theAppServerNotifierdirectly in the api endpoints that are applicable.It is not the most correct solution to the problem, but due to time constraints and urgency this will be applied first so we can move with the correct solution in a future point.
-
application crashing when clicking on files button (#28878 by @jayesh-jain252)
The application crashed when a user clicked on the files option when there were multiple files in the room.
-
Apps.engine resource consumption (#28514)
Added some validations to avoid doing unne...
6.2.0-rc.12
2023-05-15 · 1 🐛 · 1 👩💻👨💻
Engine versions
- Node:
14.21.3 - NPM:
6.14.17 - MongoDB:
4.4, 5.0, 6.0 - Apps-Engine:
1.39.0
🐛 Bug fixes
- Google Cloud Storage not working (#29244)
👩💻 👨💻 Core Team 🤓
6.2.0-rc.11
2023-05-12 · 3 🐛 · 5 🔍 · 6 👩💻👨💻
Engine versions
- Node:
14.21.3 - NPM:
6.14.17 - MongoDB:
4.4, 5.0, 6.0 - Apps-Engine:
1.39.0
🐛 Bug fixes
-
app status inconsistencies when running multiple instances in a cluster (#29220)
App status inconsistencies between multiple instances in a cluster boil down to the fact that the Apps-Engine is currently responsible for orchestrating when these events are triggered and is overly verbose in doing so.
Upon analysis, the framework itself should not have the concept of "other instances" - this is a deployment detail of the host system, and as such should be controlled by the host. The correct solution for this problem is to review this notification system, potentially removing it from the framework and leaving the responsibility solely for Rocket.Chat.
However, this is hindering the current app management experience for workspaces, so this PR cuts the control of some notifications that come from the framework (the more problematic ones) and moves the control over to RC in a short and practical way.
This is done by turning the methods of the most problematic events in the
AppActivationBridgeinto no-ops, and instead triggering theAppServerNotifierdirectly in the api endpoints that are applicable.It is not the most correct solution to the problem, but due to time constraints and urgency this will be applied first so we can move with the correct solution in a future point.
-
convert OVERWRITE_SETTING type MULTISELECT to array (#29208)
-
Migration error when removing 'snipetted' index (#29215)
🔍 Minor changes
-
improve change stream error handler (#29195)
-
regression: Delete Message Modal not closing on error in deleting a message (#29184)
This PR fixes the delete message modal on Moderation Console not closing, if an error occurs while deleting the message
-
regression: Reply in DM not working with hide_FlexTab (#29227)
-
Release 6.1.7 (#29218)
-
update Apps-Engine to latest (#29229)
Apps-Engine v1.39.0
👩💻 👨💻 Core Team 🤓
6.1.7
2023-05-12 · 2 🐛 · 2 👩💻👨💻
Engine versions
- Node:
14.21.2 - NPM:
6.14.17 - MongoDB:
4.4, 5.0, 6.0 - Apps-Engine:
1.38.3
🐛 Bug fixes
-
app status inconsistencies when running multiple instances in a cluster (#29220)
App status inconsistencies between multiple instances in a cluster boil down to the fact that the Apps-Engine is currently responsible for orchestrating when these events are triggered and is overly verbose in doing so.
Upon analysis, the framework itself should not have the concept of "other instances" - this is a deployment detail of the host system, and as such should be controlled by the host. The correct solution for this problem is to review this notification system, potentially removing it from the framework and leaving the responsibility solely for Rocket.Chat.
However, this is hindering the current app management experience for workspaces, so this PR cuts the control of some notifications that come from the framework (the more problematic ones) and moves the control over to RC in a short and practical way.
This is done by turning the methods of the most problematic events in the
AppActivationBridgeinto no-ops, and instead triggering theAppServerNotifierdirectly in the api endpoints that are applicable.It is not the most correct solution to the problem, but due to time constraints and urgency this will be applied first so we can move with the correct solution in a future point.
-
Migration error when removing 'snipetted' index (#29215)
👩💻 👨💻 Core Team 🤓
6.0.7
2023-05-12 · 2 🐛 · 2 👩💻👨💻
Engine versions
- Node:
14.21.2 - NPM:
6.14.17 - MongoDB:
4.4, 5.0, 6.0
🐛 Bug fixes
-
app status inconsistencies when running multiple instances in a cluster (#29219)
App status inconsistencies between multiple instances in a cluster boil down to the fact that the Apps-Engine is currently responsible for orchestrating when these events are triggered and is overly verbose in doing so.
Upon analysis, the framework itself should not have the concept of "other instances" - this is a deployment detail of the host system, and as such should be controlled by the host. The correct solution for this problem is to review this notification system, potentially removing it from the framework and leaving the responsibility solely for Rocket.Chat.
However, this is hindering the current app management experience for workspaces, so this PR cuts the control of some notifications that come from the framework (the more problematic ones) and moves the control over to RC in a short and practical way.
This is done by turning the methods of the most problematic events in the
AppActivationBridgeinto no-ops, and instead triggering theAppServerNotifierdirectly in the api endpoints that are applicable.It is not the most correct solution to the problem, but due to time constraints and urgency this will be applied first so we can move with the correct solution in a future point.
-
Migration error when removing 'snipetted' index (#29215)














