Rocket.Chat

Commit Graph

Author	SHA1	Message	Date
murtaza98	3f15c43a67	Bump version to 5.0.2	3 years ago
Diego Sampaio	b29a2a5e1b	Bump version to 5.0.1	3 years ago
Guilherme Gazzo	7894b12545	Bump version to 5.1.0-develop	4 years ago
murtaza98	1ad49fd86a	Bump version to 5.0.0	4 years ago
murtaza98	6a0fea4e1d	Bump version to 5.0.0-rc.12	4 years ago
Diego Sampaio	05b0e5a8d9	Bump version to 5.0.0-rc.11	4 years ago
Diego Sampaio	1cce5e4ace	Bump version to 4.8.2	4 years ago
murtaza98	4f3c3692f7	Bump version to 5.0.0-rc.10	4 years ago
murtaza98	c1142b9bf9	Bump version to 5.0.0-rc.9	4 years ago
murtaza98	b247938488	Bump version to 5.0.0-rc.8	4 years ago
murtaza98	08857ca6ba	Bump version to 5.0.0-rc.7	4 years ago
murtaza98	0cba470158	Bump version to 5.0.0-rc.6	4 years ago
murtaza98	754a6820af	Bump version to 5.0.0-rc.5	4 years ago
murtaza98	cb594578aa	Bump version to 5.0.0-rc.4	4 years ago
murtaza98	cec0bf5dfe	Bump version to 5.0.0-rc.3	4 years ago
murtaza98	3075b4dc9b	Bump version to 5.0.0-rc.2	4 years ago
Diego Sampaio	21b81e9a96	Chore: Update Meteor 2.7.3 (#25991 )	4 years ago
murtaza98	588445084e	Bump version to 5.0.0-rc.1	4 years ago
murtaza98	3b7651ba0e	Bump version to 5.0.0-rc.0	4 years ago
Guilherme Gazzo	c551240bfb	Chore: Bump deps (#25624 )	4 years ago
Tasso Evangelista	3427e5ed84	Chore: `refactor/tsc-perf` (#26040 ) Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz> Co-authored-by: Pierre Lehnen <pierre.lehnen@rocket.chat> Co-authored-by: Guilherme Gazzo <guilhermegazzo@gmail.com>	4 years ago
Guilherme Gazzo	3544ed0a73	Chore: Revert `yarn dev` implementation (#26075 )	4 years ago
gabriellsh	016584b599	[FIX] Too many watchers in dev environment. (#25930 ) <!-- 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... -->	4 years ago
Guilherme Gazzo	02bd756dc5	Chore: Update poplib (#25964 )	4 years ago
Pierre Lehnen	d0078fefab	Chore: Keep the option to run only the meteor app (#25915 ) <!-- 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... -->	4 years ago
Kevin Aleman	d6f4d1b238	[FIX] Update chartjs usage to v3 (#25873 ) <!-- 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... -->	4 years ago
gabriellsh	06043f52cc	Chore: Watch for package changes (#25910 ) <!-- 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. --> With the current `dev` pipeline, whenever we modify a package (e.g. `api-client`), we have to kill the meteor proccess and run `yarn dev` again in order for the changes to be compiled and the new output to be used by meteor. This has the drawback of taking a little longer to run the dev environment, since we can't cache a watched buid. In the other hand, it reduces the friction of modifying internal packages since we don't need to rebuild the project for changes to take effect. This will enable us to move more things to separate packages without affecting the dev experience too much. <!-- 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... -->	4 years ago
Diego Sampaio	22383aaab1	Chore: Fix version on develop branch (#25842 )	4 years ago
Murtaza Patrawala	92a2579518	Chore: Remove snap files from Houston config (#25819 ) <!-- 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 --> Since these snap files were recently removed [here](https://github.com/RocketChat/Rocket.Chat/pull/25790), we'd need to update out release CLI accordingly ## 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... -->	4 years ago
Guilherme Gazzo	7701b40f5f	Bump version to 4.8.1	4 years ago
Douglas Gubert	ad67cd3ff5	Merge master into develop & Set version to 5.0.0 (#25702 )	4 years ago
Douglas Gubert	fc5b1eafe6	Bump version to 4.8.0	4 years ago
Douglas Gubert	7b2edbf405	Bump version to 4.8.0-rc.5	4 years ago
Douglas Gubert	666825bfb7	Bump version to 4.8.0-rc.4	4 years ago
Douglas Gubert	92b0b7e2f4	Bump version to 4.8.0-rc.3	4 years ago
Douglas Gubert	a7f104b2c2	Bump version to 4.8.0-rc.2	4 years ago
Douglas Gubert	2f637c7bb3	Bump version to 4.8.0-rc.1	4 years ago
Douglas Gubert	13477d7e47	Bump version to 4.8.0-rc.0	4 years ago
Alan Sikora	b4f22e3da7	[NEW] Federation (Alpha Stabilization) (#25457 ) * adding settings file back * added js-yaml types * [IMPROVE] Stabilization on federated rooms (#25571) * chore: (wip) fixing proxy events handlers * chore: fix lint * fix: remove race condition + remove inline method * improve: general improvements for the mvp Co-authored-by: Marcos Defendi <marcos.defendi@rocket.chat> Co-authored-by: Aaron Ogle <aaron@geekgonecrazy.com>	4 years ago
Douglas Gubert	a9fc18a450	Bump version to 4.7.2	4 years ago
Douglas Gubert	0126e82ab1	Bump version to 4.7.1	4 years ago
Diego Sampaio	1b9a5f0984	Chore: Move ddp-streamer micro service to its own sub-repo (#25246 )	4 years ago
Tasso Evangelista	2b8600aa6c	Chore: Update Volta configuration (#25394 )	4 years ago
Douglas Gubert	1b4cdf4c3f	Bump version to 4.8.0-develop	4 years ago
Douglas Gubert	18c437659e	Bump version to 4.7.0	4 years ago
Douglas Gubert	2059a0e1e6	Bump version to 4.7.0-rc.5	4 years ago
Douglas Gubert	48827f3211	Bump version to 4.7.0-rc.4	4 years ago
Douglas Gubert	1e37adef4b	Bump version to 4.7.0-rc.3	4 years ago
Douglas Gubert	1ae769301e	Bump version to 4.7.0-rc.2	4 years ago
Douglas Gubert	3785841489	Bump version to 4.7.0-rc.1	4 years ago

1 2 3 4 5 ...

1222 Commits (Export-PDF-Transcript)