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

[Issue #2415] Bump mysql2 version #2418

Merged
merged 5 commits into from
Jul 2, 2024
Merged

Conversation

nicholas-lockhart
Copy link
Contributor

Thanks for contribution! Please go through following checklist before sending PR.

PR Branch Destination

  • For Azurite V3, please send PR to main branch.
  • For legacy Azurite V2, please send PR to legacy-dev branch.

Always Add Test Cases

Make sure test cases are added to cover the code change.

Add Change Log

Add change log for the code change in Upcoming Release section in ChangeLog.md.

Development Guideline

Please go to CONTRIBUTION.md for steps about setting up development environment and recommended Visual Studio Code extensions.

@nicholas-lockhart
Copy link
Contributor Author

nicholas-lockhart commented Jun 26, 2024 via email

@blueww
Copy link
Member

blueww commented Jun 27, 2024

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

"version": "3.7.0",
"resolved": "https://registry.npmjs.org/mysql2/-/mysql2-3.7.0.tgz",
"integrity": "sha512-c45jA3Jc1X8yJKzrWu1GpplBKGwv/wIV6ITZTlCSY7npF2YfJR+6nMP5e+NTQhUeJPSyOQAbGDCGEHbAl8HN9w==",
"version": "3.10.1",
Copy link
Member

Choose a reason for hiding this comment

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

Please also update package.json.
And please rebase or merge the latest main.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

package.json is not necessary to change since the ^ notation allows for any minor version bump without going to 4.0.0. If you look at Main now, you will see that package.json is showing ^3.2.0 but the lock is resolving to 3.7.0. Looking at the blame, the package.json was updated a year ago when mysql2 made a major jump (2.1.0 -> 3.2.0). The package-lock.json has bumped twice (3.2.0 -> 3.6.3 -> 3.7.0) since that time.

If you are truly passionate about this change, even though it doesn't follow the historical pattern of the project, I am fine with making the change.

Copy link
Member

Choose a reason for hiding this comment

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

We would recommend to also update package.json.
Or remove package-lock.json and run "npm install" will masql2 will still use 3.7.0.
So it's better to also update package.json to make sure the correct version will be used.
Thanks!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated

@blueww blueww merged commit ef2e312 into Azure:main Jul 2, 2024
35 checks passed
@blueww
Copy link
Member

blueww commented Jul 2, 2024

@nicholas-lockhart

Thanks for your contribution!
The PR is merged.

@nicholas-lockhart
Copy link
Contributor Author

Thanks for the help, @blueww

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.

2 participants