Skip to content
Snippets Groups Projects
Unverified Commit 9dc1455b authored by Diego Sampaio's avatar Diego Sampaio
Browse files

Bump version to 6.1.2

parent c681b8e7
No related branches found
No related tags found
No related merge requests found
   
# 6.1.2
`2023-04-13 · 4 🐛 · 3 🔍 · 11 👩‍💻👨‍💻`
### Engine versions
- Node: `14.21.2`
- NPM: `6.14.17`
- MongoDB: `4.4, 5.0, 6.0`
- Apps-Engine: `1.38.1`
### 🐛 Bug fixes
- Add function to get installation source ([#28806](https://github.com/RocketChat/Rocket.Chat/pull/28806))
There have been reports of problems regarding the missing information of `installationSource` in 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
- Fixed no role assign to manual registered users despite of Default Roles for Users settings ([#28293](https://github.com/RocketChat/Rocket.Chat/pull/28293) by [@bhardwajdisha](https://github.com/bhardwajdisha))
- Quotes chain off by one error in quote chain limit settings ([#28281](https://github.com/RocketChat/Rocket.Chat/pull/28281) by [@jayesh-jain252](https://github.com/jayesh-jain252))
Fixed off by one error in Quote Chain Limit. Now if a user sets Message_QuoteChainLimit (default is 2) the number of quotes chained matches the setting.
Changes are made in apps/meteor/app/oembed/server/jumpToMessage.ts file
With Message_QuoteChainLimit=2
Before:
![quote_limit2_before](https://user-images.githubusercontent.com/79307894/222970577-5d2b2dc9-c191-4758-acea-909786d974ac.PNG)
After:
![quote_limit2_after](https://user-images.githubusercontent.com/79307894/222970247-fa0bcfcf-e7f3-4102-b7b3-820fb43677c1.PNG)
- SMTP warnings on user form ([#28832](https://github.com/RocketChat/Rocket.Chat/pull/28832))
Check for SMTP config on server side and then show warning on client side
<details>
<summary>🔍 Minor changes</summary>
- Add `rid` to scope of `create-invite-links` permission check ([#28241](https://github.com/RocketChat/Rocket.Chat/pull/28241))
This PR fixes a bug where users with the `owner` role can't create invites because the button isn't being displayed for him, to solve this issue the `rid` was added to the scope of the check.
- bump apps-engine version to 1.38.1 ([#28885](https://github.com/RocketChat/Rocket.Chat/pull/28885))
- Upgrade `vm2` ([#28860](https://github.com/RocketChat/Rocket.Chat/pull/28860))
It patches `vm2`.
</details>
### 👩‍💻👨‍💻 Contributors 😍
- [@bhardwajdisha](https://github.com/bhardwajdisha)
- [@jayesh-jain252](https://github.com/jayesh-jain252)
### 👩‍💻👨‍💻 Core Team 🤓
- [@LucianoPierdona](https://github.com/LucianoPierdona)
- [@casalsgh](https://github.com/casalsgh)
- [@d-gubert](https://github.com/d-gubert)
- [@hugocostadev](https://github.com/hugocostadev)
- [@matheusbsilva137](https://github.com/matheusbsilva137)
- [@sampaiodiego](https://github.com/sampaiodiego)
- [@tapiarafael](https://github.com/tapiarafael)
- [@tassoevan](https://github.com/tassoevan)
- [@yash-rajpal](https://github.com/yash-rajpal)
# 6.1.1 # 6.1.1
`2023-04-04 · 1 🐛 · 3 👩‍💻👨‍💻` `2023-04-04 · 1 🐛 · 3 👩‍💻👨‍💻`
   
FROM registry.access.redhat.com/ubi8/nodejs-12 FROM registry.access.redhat.com/ubi8/nodejs-12
ENV RC_VERSION 6.1.1 ENV RC_VERSION 6.1.2
MAINTAINER buildmaster@rocket.chat MAINTAINER buildmaster@rocket.chat
......
{ {
"version": "6.1.1" "version": "6.1.2"
} }
{ {
"name": "@rocket.chat/meteor", "name": "@rocket.chat/meteor",
"description": "The Ultimate Open Source WebChat Platform", "description": "The Ultimate Open Source WebChat Platform",
"version": "6.1.1", "version": "6.1.2",
"private": true, "private": true,
"author": { "author": {
"name": "Rocket.Chat", "name": "Rocket.Chat",
......
{ {
"name": "rocket.chat", "name": "rocket.chat",
"version": "6.1.1", "version": "6.1.2",
"description": "Rocket.Chat Monorepo", "description": "Rocket.Chat Monorepo",
"main": "index.js", "main": "index.js",
"private": true, "private": true,
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment