Skip to content

Hyperdrive MySQL GA Changelog - #32351

Draft
ivoryibu wants to merge 1 commit into
productionfrom
hyperdrive-mysql-ga-changelog
Draft

Hyperdrive MySQL GA Changelog#32351
ivoryibu wants to merge 1 commit into
productionfrom
hyperdrive-mysql-ga-changelog

Conversation

@ivoryibu

Copy link
Copy Markdown
Collaborator

Adds a changelog entry announcing the general availability of MySQL support in Hyperdrive, post-dated to 2026-08-03.

  • Reuses the established Hyperdrive changelog prose and mysql2 (Promise API) code example, wrapped in TypeScriptExample to auto-generate a JS tab.
  • Notes that MySQL GA is available on the same Hyperdrive plans as Postgres, with a link to the pricing page.
  • Links to how Hyperdrive works and the get started guide.

@ivoryibu
ivoryibu requested review from a team and hoan-pom as code owners July 28, 2026 03:59
@cloudflare-docs-bot

cloudflare-docs-bot Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Review

⚠️ 1 warning, 💡 1 suggestion found in commit bece859.

👉 Fix in your agent 👈
Fix the following review findings in PR #32351 (https://github.com/cloudflare/cloudflare-docs/pull/32351).

Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g. the fix requires disproportionate effort for minimal benefit,
  or the finding is factually incorrect), explain why
- If you need clarification before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order

After triaging, follow this order:
1. Post a comment on this PR for any findings you are skipping, with the finding ID and your reasoning.
2. Then commit the fixes for the legitimate findings.

The comment must come before the commit — the bot reads PR comments when a new
push triggers a review, so skip comments posted after the push will be missed.

---

## Code Review

### Warnings (1)

#### CR-1df323061fc3 · Resource leak on error path
- **File:** `src/content/changelog/hyperdrive/2026-08-03-hyperdrive-mysql-ga.mdx` line 37
- **Issue:** If `connection.query("SHOW tables;")` throws, the MySQL connection created on line 28 is never closed because `ctx.waitUntil(connection.end())` is only reached on the success path.
- **Fix:** Wrap the query in a `try`/`finally` (or `try`/`catch` as shown in `src/content/docs/hyperdrive/get-started.mdx`) so `connection.end()` runs even when the query fails.

---

## Style Guide Review

### Suggestions (1)

#### SG-9bd5ee608e29 · Avoid 'Learn more about...' before a link
- **File:** `src/content/changelog/hyperdrive/2026-08-03-hyperdrive-mysql-ga.mdx` line 53
- **Issue:** Line uses 'Learn more about [how Hyperdrive works](/hyperdrive/concepts/how-hyperdrive-works/) and [get started building Workers that connect to MySQL with Hyperdrive](/hyperdrive/get-started/).'
- **Fix:** Use 'For more information, refer to [How Hyperdrive works](/hyperdrive/concepts/how-hyperdrive-works/) and [Get started with Hyperdrive and MySQL](/hyperdrive/get-started/).'

Code Review

This code review is in beta and may not always be helpful — use your judgment.

Warnings (1)
File Issue
changelog/hyperdrive/2026-08-03-hyperdrive-mysql-ga.mdx line 37 Resource leak on error path — If connection.query("SHOW tables;") throws, the MySQL connection created on line 28 is never closed because ctx.waitUntil(connection.end()) is only reached on the success path. Fix: Wrap the query in a try/finally (or try/catch as shown in src/content/docs/hyperdrive/get-started.mdx) so connection.end() runs even when the query fails.

Conventions

No convention issues found.

Style Guide Review

Suggestions (1)
File Issue
changelog/hyperdrive/2026-08-03-hyperdrive-mysql-ga.mdx line 53 Avoid 'Learn more about...' before a link — Line uses 'Learn more about how Hyperdrive works and get started building Workers that connect to MySQL with Hyperdrive.' Fix: Use 'For more information, refer to How Hyperdrive works and Get started with Hyperdrive and MySQL.'
Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command Description
/review Runs a review now. Incremental if a prior review exists, full if not.
/full-review Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.
/ignore-review-limit Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.
/disable-auto-review Stops automatic reviews from triggering on future pushes to this PR. Codeowners can still run /review or /full-review manually.
/rebase Rebases the PR branch against production. On conflict, attempts to resolve automatically using AI. Stops with an explanation if confidence is not high enough.

@github-actions

Copy link
Copy Markdown
Contributor

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
/src/content/changelog/ @cloudflare/pm-changelogs, @cloudflare/product-owners, @hoan-pom

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants