You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please do not report security vulnerabilities here. The Responsible Disclosure Program details the procedure for disclosing security issues.
Thank you in advance for helping us to improve this library! Your attention to detail here is greatly appreciated and will help us respond as quickly as possible. For general support or usage questions, use the Auth0 Community or Auth0 Support. Finally, to avoid duplicates, please search existing Issues before submitting one here.
By submitting an Issue to this repository, you agree to the terms within the Auth0 Code of Conduct.
Describe the problem you'd like to have solved
Would it possible to update the Auth0 dependency of Lock to v.2.0 or higher? Just because we'd like to utilize the latest concurrency features with Auth0.
Describe the ideal solution
N/A
Alternatives and current work-arounds
As an alternative, our team can always setup the login screen from scratch and utilize the latest Auth0 version. But we'd like to stick to Lock and are hoping it can update with the latest Auth0 version.
Additional context
N/A.
The text was updated successfully, but these errors were encountered:
Please do not report security vulnerabilities here. The Responsible Disclosure Program details the procedure for disclosing security issues.
Thank you in advance for helping us to improve this library! Your attention to detail here is greatly appreciated and will help us respond as quickly as possible. For general support or usage questions, use the Auth0 Community or Auth0 Support. Finally, to avoid duplicates, please search existing Issues before submitting one here.
By submitting an Issue to this repository, you agree to the terms within the Auth0 Code of Conduct.
Describe the problem you'd like to have solved
Would it possible to update the
Auth0
dependency of Lock to v.2.0 or higher? Just because we'd like to utilize the latest concurrency features with Auth0.Describe the ideal solution
N/A
Alternatives and current work-arounds
As an alternative, our team can always setup the login screen from scratch and utilize the latest Auth0 version. But we'd like to stick to Lock and are hoping it can update with the latest Auth0 version.
Additional context
N/A.
The text was updated successfully, but these errors were encountered: