- Aug 12, 2022
-
-
Diego Sampaio authored
Release 5.0.3
-
- Aug 11, 2022
-
-
Diego Sampaio authored
-
Pierre Lehnen authored
-
Diego Sampaio authored
-
Filipe Marins authored
Co-authored-by: gabriellsh <gabriel.henriques@rocket.chat>
-
Kevin Aleman authored
Co-authored-by: Murtaza Patrawala <34130764+murtaza98@users.noreply.github.com> Co-authored-by: Guilherme Gazzo <5263975+ggazzo@users.noreply.github.com>
-
- Aug 08, 2022
-
-
Diego Sampaio authored
Release 5.0.2
-
murtaza98 authored
-
Fábio Albuquerque authored
Co-authored-by: Diego Sampaio <8591547+sampaiodiego@users.noreply.github.com>
-
Martin Schoeler authored
-
- Aug 02, 2022
-
-
Diego Sampaio authored
Release 5.0.1
-
Diego Sampaio authored
-
Douglas Fabris authored
-
Diego Sampaio authored
-
Henrique Guimarães Ribeiro authored
-
Douglas Fabris authored
-
Douglas Fabris authored
-
- Jul 21, 2022
-
-
Diego Sampaio authored
Release 5.0.0
-
murtaza98 authored
-
murtaza98 authored
-
murtaza98 authored
-
Murtaza Patrawala authored
Co-authored-by: Aleksander Nicacio da Silva <aleksander.silva@rocket.chat> Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz>
-
Douglas Fabris authored
Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz>
-
Júlia Jaeger Foresti authored
Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz>
-
Diego Sampaio authored
-
Diego Sampaio authored
-
Diego Sampaio authored
-
Diego Sampaio authored
-
Diego Sampaio authored
Release 4.8.2
-
Diego Sampaio authored
-
- Jul 20, 2022
-
-
Carlos Rodrigues authored
Co-authored-by: Matheus Barbosa Silva <36537004+matheusbsilva137@users.noreply.github.com> Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz>
-
Diego Sampaio authored
-
matthias4217 authored
Co-authored-by: Diego Sampaio <chinello@gmail.com>
-
Diego Sampaio authored
[FIX] Error "numRequestsAllowed" property in rateLimiter for REST API endpoint when upgrading (#26058) <!-- This is a pull request template, you do not need to uncomment or remove the comments, they won't show up in the PR text. --> <!-- Your Pull Request name should start with one of the following tags [NEW] For new features [IMPROVE] For an improvement (performance or little improvements) in existing features [FIX] For bug fixes that affect the end-user [BREAK] For pull requests including breaking changes Chore: For small tasks Doc: For documentation --> <!-- Checklist!!! If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. - I have read the Contributing Guide - https://github.com/RocketChat/Rocket.Chat/blob/develop/.github/CONTRIBUTING.md#contributing-to-rocketchat doc - I have signed the CLA - https://cla-assistant.io/RocketChat/Rocket.Chat - Lint and unit tests pass locally with my changes - I have added tests that prove my fix is effective or that my feature works (if applicable) - I have added necessary documentation (if applicable) - Any dependent changes have been merged and published in downstream modules --> ## Proposed changes (including videos or screenshots) <!-- CHANGELOG --> <!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue below. This description will appear in the release notes if we accept the contribution. --> <!-- END CHANGELOG --> ## Issue(s) <!-- Link the issues being closed by or related to this PR. For example, you can use #594 if this PR closes issue number 594 --> ## Steps to test or reproduce <!-- Mention how you would reproduce the bug if not mentioned on the issue page already. Also mention which screens are going to have the changes if applicable --> ## Further comments <!-- If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... -->
-
Diego Sampaio authored
<!-- This is a pull request template, you do not need to uncomment or remove the comments, they won't show up in the PR text. --> <!-- Your Pull Request name should start with one of the following tags [NEW] For new features [IMPROVE] For an improvement (performance or little improvements) in existing features [FIX] For bug fixes that affect the end-user [BREAK] For pull requests including breaking changes Chore: For small tasks Doc: For documentation --> <!-- Checklist!!! If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. - I have read the Contributing Guide - https://github.com/RocketChat/Rocket.Chat/blob/develop/.github/CONTRIBUTING.md#contributing-to-rocketchat doc - I have signed the CLA - https://cla-assistant.io/RocketChat/Rocket.Chat - Lint and unit tests pass locally with my changes - I have added tests that prove my fix is effective or that my feature works (if applicable) - I have added necessary documentation (if applicable) - Any dependent changes have been merged and published in downstream modules --> ## Proposed changes (including videos or screenshots) <!-- CHANGELOG --> <!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue below. This description will appear in the release notes if we accept the contribution. --> <!-- END CHANGELOG --> ## Issue(s) <!-- Link the issues being closed by or related to this PR. For example, you can use #594 if this PR closes issue number 594 --> ## Steps to test or reproduce <!-- Mention how you would reproduce the bug if not mentioned on the issue page already. Also mention which screens are going to have the changes if applicable --> ## Further comments <!-- If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... -->
-
gabriellsh authored
-
Marcos Spessatto Defendi authored
-
Tiago Evangelista Pinto authored
-
Luciano Marcos Pierdona Junior authored
Co-authored-by: Tasso Evangelista <tasso.evangelista@rocket.chat> Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>
-
Murtaza Patrawala authored
-