Skip to content
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

[FIX] Broken settings check for updates #27779

Merged
merged 4 commits into from
Feb 14, 2023
Merged

Conversation

geekgonecrazy
Copy link
Contributor

Proposed changes (including videos or screenshots)

If someone choses not to register but still want to find out about new versions, or critical vulnerabilities this code would never fire.

Issue(s)

Steps to test or reproduce

Further comments

@debdutdeb debdutdeb changed the title [Fix] Broken settings check for updates [FIX] Broken settings check for updates Jan 17, 2023
Co-authored-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
Copy link
Member

@debdutdeb debdutdeb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

makes sense to me :)

@geekgonecrazy geekgonecrazy added this to the 6.0.0 milestone Jan 27, 2023
Copy link
Contributor

@KevLehman KevLehman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this have any form of QA?

@debdutdeb
Copy link
Member

debdutdeb commented Feb 11, 2023

I honestly don't see the need for this patch 😬 as long as the CI is comfortable

@sampaiodiego sampaiodiego merged commit 548f449 into develop Feb 14, 2023
@sampaiodiego sampaiodiego deleted the vulnerability-check branch February 14, 2023 01:34
@sampaiodiego sampaiodiego mentioned this pull request Feb 17, 2023
@sampaiodiego sampaiodiego mentioned this pull request Mar 9, 2023
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants