-
Notifications
You must be signed in to change notification settings - Fork 13k
Release 7.9.1 #36584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 7.9.1 #36584
Conversation
🦋 Changeset detectedLatest commit: 64de34f The changes in this PR will be included in the next version bump. This PR includes changesets to release 37 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Looks like this PR is not ready to merge, because of the following issues:
Please fix the issues and try again If you have any trouble, please check the PR guidelines |
…en transfering (#36581) Co-authored-by: Kevin Aleman <kaleman960@gmail.com>
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #36584 +/- ##
=======================================
Coverage 65.70% 65.71%
=======================================
Files 3172 3172
Lines 105574 105574
Branches 20087 20027 -60
=======================================
+ Hits 69370 69379 +9
+ Misses 33533 33523 -10
- Partials 2671 2672 +1
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Co-authored-by: Matheus Cardoso <matheus@cardo.so> Co-authored-by: Jessica Schelly Souza <jessica_schelly@hotmail.com>
You can see below a preview of the release change log:
7.9.1
Engine versions
22.16.01.43.55.0, 6.0, 7.01.54.0Patch Changes
Bump @rocket.chat/meteor version.
(#36581 by @dionisio-bot) Fixes an issue where rooms transferred to a department's queue could get stuck—marked as taken but with no agent assigned.
(#36612 by @dionisio-bot) Fixes a bug where the
/api/v1/users.updateAPI call was replacing the entirecustomFieldsobject instead of merging only the specified properties. The fix ensures that when updating custom fields, existing values are preserved while only specified fields are updated or added.Updated dependencies []: