-
Notifications
You must be signed in to change notification settings - Fork 333
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
Update mysql2 version #2415
Comments
Thanks for raising the issue! Do you mean mysql client, Azurite currently refer to We are currently working on some other new features and improvements, so this might won't be our recent priority. Azurite welcome contribution! |
Yes, the mysql client is the dependency in question. You can see here that is resolves to 3.7.0 for this project. Looking at NPM's versions available, it can be seen that there is now a 3.10.1 version available which has been a popular download, assuming it fixed some security issues based on the download count trends. |
Azurite welcome contribution! We are currently working on some other new features and improvements, so this might won't be our recent priority. |
Close as the fix PR is merged. #2418 |
Which service(blob, file, queue, table) does this issue concern?
N/A
Which version of the Azurite was used?
Azurite 3.30.0
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
DockerHub
mcr.microsoft.com/azure-storage/azurite:3.30.0
What's the Node.js version?
v20.10.0
What problem was encountered?
I noticed that the version of mysql2 (3.7.0) being used is several months old. I know that there were a couple of significant CVEs that were resolved in 3.9.7, and there was a new version created not too long ago (3.10.0).
When do we think that Azurite will be using a newer version of mysql2 for testing?
Steps to reproduce the issue?
N/A
Have you found a mitigation/solution?
The text was updated successfully, but these errors were encountered: