Bump mysql2 from 3.24.3 to 3.24.4

[dependabot]

Bumps mysql2 from 3.24.3 to 3.24.4.

Release notes

Sourced from mysql2's releases.

v3.24.4

3.24.4 (2026-09-07)

Performance Improvements

• per-query overhead, local dates, short strings, TLS context and compression (#4522) (2387daf)
• reuse TLS sessions across connections to the same server (#4529) (9178c82)

Changelog

Sourced from mysql2's changelog.

3.24.4 (2026-09-07)

Performance Improvements

• per-query overhead, local dates, short strings, TLS context and compression (#4522) (2387daf)
• reuse TLS sessions across connections to the same server (#4529) (9178c82)

Commits

• a87208a chore(master): release 3.24.4 (#4530)
• e5833be chore: prepare src for parallel TypeScript transcription (#4538)
• 5f6482f build(deps): bump sass from 1.103.1 to 1.104.0 in /website (#4537)
• 8e0bd84 build(deps): bump lucide-react from 1.38.0 to 1.41.0 in /website (#4536)
• 8b8a9cb build(deps-dev): bump @​types/node from 26.4.0 to 26.4.1 in /website (#4535)
• 83854a6 build(deps): bump docusaurus-plugin-sass (#4534)
• 2e9d75a build(deps-dev): bump @​biomejs/biome from 2.5.11 to 2.5.12 (#4533)
• d6f4172 build(deps-dev): bump @​types/node from 26.4.0 to 26.4.1 (#4532)
• 2e1c9e0 build(deps): bump lru.min from 1.1.4 to 1.1.5 (#4531)
• 2387daf perf: per-query overhead, local dates, short strings, TLS context and compres...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Akanksha Jain (jainakanksha-msft)]

Copilot This PR was opened by Dependabot. Please take it the rest of the way before it's ready for human review:

1. Impact analysis — review the PR diff/description to identify what changed, including the package name and old → new version, then check where that dependency is actually used in the codebase, or whether it is unused, and summarize the potential impact.
2. Fix build/conflict issues — run npm ci --legacy-peer-deps, npm run build, and npm run lint; resolve any merge conflicts, build errors, or lint errors that surface.
3. Tests — add or update tests under tests/** to cover the changed usage, and make sure they meaningfully validate the change (not just re-assert the version bump).
4. Run the suite — run the relevant npm run test:* script(s) for the affected area (e.g. test:blob, test:queue, test:table) and keep fixing until they pass.
5. Changelog — append one bullet to ChangeLog.md under ## Upcoming Release → General:, matching the existing style and tone of the entries already there (package name in backticks, old → new version, why, and a one-line concise summary of any code changes made).
6. Comments — review any existing PR comments and review threads, including resolved/hidden ones, and address anything actionable.
7. Self-rate — rate this work 1-10 against: correctness, test coverage, changelog accuracy, build/lint health, and comment resolution.
8. Iterate — if it's not a 10, keep improving until it is before finishing.
9. Summary — your final response must use the following structure exactly (no free-form paragraph summary).

Impact analysis

• Package:
• Old version:
• New version:
• Change Impact:

Build/Conflict Issues

• Commands:
• Result:

Tests

• Added:
• Updated:
• Result:

Run the Suite

• Commands:
• Status:

Changelog

• Entry:
• Location:

Comments

• Reviewed:
• Actions:

Self-Rate

• Score:
• Reasoning:

Summary

• Why this matters:
• Risk of not taking change:

[Copilot]

Copilot This PR was opened by Dependabot. Please take it the rest of the way before it's ready for human review:

1. Impact analysis — review the PR diff/description to identify what changed, i...

Completed the requested dependency analysis and validation. Commit c3f19c8 adds the Upcoming Release entry; existing Blob SQL metadata-store driver coverage was exercised against mysql2 3.24.4, so no dependency-only test was added.