Skip to content

Commit 5f004f0

Browse files
committed
v2.24.4: Speed up getSchemaWeights() by ~20x on large DBs
1 parent c3002ff commit 5f004f0

File tree

4 files changed

+211
-229
lines changed

4 files changed

+211
-229
lines changed

SECURITY.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ ClickUp defines a security vulnerability as an unintended weakness or exposure t
2424

2525
## Vulnerability Reporting
2626

27-
ClickUp recommends that you share the details of any suspected vulnerabilities across any asset owned, controlled, or operated by ClickUp (or that would reasonably impact the security of ClickUp and our users) using our vulnerability disclosure form at <http://clickup.com/bug-bounty>. The ClickUp Security team will acknowledge receipt of each valid vulnerability report, conduct a thorough investigation, and then take appropriate action for resolution.
27+
ClickUp recommends that you share the details of any suspected vulnerabilities across any asset owned, controlled, or operated by ClickUp (or that would reasonably impact the security of ClickUp and our users) using our vulnerability disclosure form at <https://clickup.com/vulnerability-disclosure>. The ClickUp Security team will acknowledge receipt of each valid vulnerability report, conduct a thorough investigation, and then take appropriate action for resolution.
2828

2929
## Safe Harbor
3030

@@ -36,4 +36,4 @@ When conducting vulnerability research according to this policy, we consider thi
3636
- Lawful, helpful to the overall security of the Internet, and conducted in good faith.
3737
- You are expected, as always, to comply with all applicable laws.
3838

39-
If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please inquire via <support@bugcrowd.com> before going any further.
39+
If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please inquire via HackerOne Support team before going any further.

0 commit comments

Comments
 (0)