docs(changelog): v1.15.0 release notes (back-dated to 2026-07-30)

[ajitpratap0]

Summary

Adds a [1.15.0] - 2026-07-30 section to CHANGELOG.md. v1.15.0 is tagged at 31b5b1c, the last main commit before the October perf/fix sprint, with the tag date set back to 2026-07-30.

After #598 consolidated the changelog, the v1.15.0-scope entries sat under [Unreleased]. This PR moves the 24 entries that cite only #509–#518 or #528 into [1.15.0], keeping their wording. Four entries that cited both v1.15.0 PRs and later ones are split by PR:

• SplitStatements: the API moves to v1.15.0; the perf(gosqlx): make SplitStatements slice the source instead of copying every byte through strings.Builder (#559) #569 perf note stays in Performance.
• Internal CI, website and docs bullets.

The [Unreleased] intro now says it covers changes since v1.15.0. A footer compare link is added for [1.15.0].

Test Plan

• Docs-only change; no Go files touched.
• A script confirmed no [Unreleased] entry still references chore(integrations): bump to GoSQLX v1.14.0 #509–fix: architect-review sprint 2 — all 5 sprints in one PR #518 or fix(security): resolve new Trivy Repository Scan CVEs blocking CI #528.
• Vercel preview: /blog shows a v1.15.0 post, generated from the changelog section by split-changelog.js.

Breaking Changes

None in this PR. The v1.15.0 notes keep the existing Behavior changes subsection.

🤖 Generated with Claude Code

https://claude.ai/code/session_01RkzVu3JY9Y6BRWfjesWts9

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
gosqlx-website	Ready	Preview	Oct 14, 2026 12:34pm UTC

[github-actions]

Claude finished @ajitpratap0's task in 24s —— View job

---

Review of PR #633 (CHANGELOG v1.15.0)

Verdict: looks good, with a few minor notes.

• Read the diff and compared the new heading with website/scripts/split-changelog.js

What I checked

• The ## [1.15.0] - 2026-07-30 — … heading uses the same format as [1.14.0]. It matches versionRegex in split-changelog.js:20, so the blog post should generate. The Vercel preview is still worth a look, as your test plan says.
• The section follows Keep a Changelog structure (Added, Changed, Fixed, Deprecated, Security), and [Unreleased] still holds only feat(cli): add --dialect flag to parse, format, analyze, lint #526 and later.
• Footer links are correct. [Unreleased] now compares from v1.15.0, and the missing [1.14.0] link is added. The [1.15.0] compare range is v1.14.0...v1.15.0.

Notes

1. Tag not verified. The CI checkout is shallow and has no tags. 31b5b1c isn't a valid object here, and git tag shows no v1.15.0 or v1.14.0. The compare links only work once v1.15.0 is pushed at 31b5b1c. Per CLAUDE.md, tag after this docs PR merges. I also couldn't re-verify the API names against that commit, so I'm relying on your git grep check.

2. Possible overclaim in the intro. "Upgrade from v1.14.0 is additive for the public API" sits uneasily with the Changed section:

   • Snowflake stubs now return *ast.UnsupportedStatement, which breaks exhaustive type switches.
   • ValidateBytes now rejects empty input.
   • *errors.Error WithX methods became copy-on-write, so code relying on mutation of the receiver would break.

   Consider "additive except for the behaviour changes listed under Changed". The PR body calls the first two out as behaviour changes but the intro doesn't.

3. Headline vs. body wording. The title says "ClickHouse 100%", but the body says 83/83 of the QA corpus. The body is accurate, so consider "ClickHouse QA corpus 83/83" in the heading to avoid implying full ClickHouse coverage. It's a nit.

4. Back-dated date. The date 2026-07-30 is earlier than the October merges still sitting in [Unreleased]. That's intentional, but the changelog now has a release dated before commits that appear above it. A one-line note in the PR or release body saying the tag is back-dated would help future readers. The Deprecated removal wording ("v2.0") is fine.

5. Missing #-references. Several entries lack PR numbers (the AST and Dialects sub-bullets partly, and the Website bullet lists three). This is purely cosmetic.

Docs-only, no security or performance concerns, and no Go tests are applicable.
· branch docs/v1.15.0-release

[github-actions]

Claude finished @ajitpratap0's task in 20s —— View job

---

Review of PR #633 (CHANGELOG v1.15.0)

Verdict: looks good. Only nits remain.

This is a docs-only change. I read the full diff against origin/main. I didn't run Go tests, since no Go files changed. I also couldn't check API names against 31b5b1c, because the CI checkout has no tags or history. I'm relying on your git grep check.

Checked and fine

• Entries moved, not duplicated: the v1.15.0 entries (fix(ast): replace DescribeStatement stubs with UnsupportedStatement, fix extraction gaps #511–fix: architect-review sprint 2 — all 5 sprints in one PR #518, fix(security): resolve new Trivy Repository Scan CVEs blocking CI #528) were cut from [Unreleased] and moved into the new section. I found none left behind and none duplicated.
• [Unreleased] intro: it now says "since v1.15.0". It keeps the "source-compatible" claim and points readers to Behavior changes. That section still holds the October items.
• v1.15.0 intro: it reads "Exported signatures are unchanged apart from additions; read Behavior changes before upgrading". The section has its own Behavior changes block covering linter nesting, structured errors, ValidateBytes("") and the Snowflake stubs. This addresses the earlier "additive" overclaim concern.
• Footer links: [Unreleased] compares from v1.15.0, [1.15.0] compares v1.14.0...v1.15.0, and the missing [1.14.0] link is added.
• Heading format: it matches the [1.14.0] style, so split-changelog.js should generate the post. Please still check the Vercel preview, as your test plan says.

Nits (non-blocking)

1. Heading wording: "ClickHouse 100%" in the heading is stronger than the body, which says 83/83 of the QA corpus. Consider "ClickHouse QA Corpus 83/83".
2. Behavior change not listed: the *errors.Error WithX copy-on-write change is listed, but only inside the "Structured parser errors" bullet. Code that relied on mutating the receiver would break. A separate bullet or an explicit "returns a copy" note would make it easier to find.
3. Tag must come first: both compare links return 404 until v1.15.0 is pushed at 31b5b1c. Per CLAUDE.md, tag after this PR merges. Because the date is back-dated, note that in the GitHub release body.
4. Order in the file: [Unreleased] now holds October work above a section dated 2026-07-30. That is correct given the back-dated tag, but the date will look odd to readers.
5. Missing PR numbers: a few bullets have none. For example, the Internal entries for the website and docs list only some PRs. This is cosmetic.

No security or performance concerns.
· branch docs/v1.15.0-release

[github-actions]

Claude finished @ajitpratap0's task in 23s —— View job

---

Review of PR #633 (CHANGELOG v1.15.0)

Verdict: looks good. No blocking issues.

• Read the diff against origin/main
• Checked the headings, intros and footer links

What I checked

• ## [1.15.0] - 2026-07-30 — … (line 505) uses the same heading format as [1.14.0], so split-changelog.js should pick it up. The Vercel /blog preview is still worth checking, as your test plan says.
• No #509–#518 or #528 references remain in the [Unreleased] section (lines 8–504).
• The [Unreleased] intro now says "since v1.15.0".
• Footer links are consistent: [Unreleased] compares v1.15.0...HEAD, [1.15.0] compares v1.14.0...v1.15.0, and [1.14.0] is present.
• The 1.15.0 intro now says "unchanged apart from additions; read Behavior changes before upgrading". That covers my earlier concern about overclaiming additive compatibility.

Notes (non-blocking)

1. The compare links only resolve once v1.15.0 is pushed at 31b5b1c. Per CLAUDE.md, tag after this PR merges. Tag the 31b5b1c commit itself, not the merge commit.
2. The heading says "ClickHouse 100%" but the body says 83/83 of the QA corpus. The body is accurate. Consider "ClickHouse QA 83/83" in the heading to avoid implying full ClickHouse coverage.
3. The release is back-dated to 2026-07-30, but October merges sit above it in the file. Put a one-line note in the GitHub release body saying the date is back-dated.
4. A few entries lack PR numbers. This is cosmetic.

This is a docs-only change, so there are no security, performance or test concerns. I could not verify the tag or the API names at 31b5b1c from the shallow CI checkout.
· branch docs/v1.15.0-release