[ajitpratap0]

Summary

Release prep for v1.16.0 (dated 2026-10-21; change the date at tag time if needed). No library behaviour changes. The only code edits are version constants and the removal of a stray file.

• CHANGELOG: [Unreleased] becomes ## [1.16.0] - 2026-10-21 — Performance Audit, SQL Highlighting, Dialect-Aware LSP, Claude Code Plugin & ChatGPT App, Correctness Sweep, with a new empty [Unreleased] above it and the compare links ([1.16.0], [Unreleased] → v1.16.0...HEAD).
  • Added the missing entries. Behavior changes: fix(tokenizer): one column per tab and token Start after trivia (#797) #826 (tab = 1 column, Start skips comments), fix(parser): parse || as logical OR in MySQL and MariaDB (#781) #790 (MySQL/MariaDB || is OR), fix(parser): composite field access and table function follow-ups (#839) #843 (composite access gated to E4001), fix(linter): report L006 column as a byte offset; tighten comment span test #840 (L006 byte column), MCP format_sql uppercasing. Added: fix(parser): composite field access and table function follow-ups (#839) #843, fix(parser): parse || as logical OR in MySQL and MariaDB (#781) #790, fix(playground): correct Analyze and Lint results from the WASM bridge #780. Fixed: fix(parser): parse arithmetic on the right-hand side of comparisons (#596) #734, fix(parser): make pooled parser capabilities match NewParser (#590) #735/fix(parser): make zero-value Parser{} capabilities match NewParser (#784) #789, fix(parser): accept general expressions in CONNECT BY (PRIOR as unary operator) #791, fix(ast): render Snowflake VariantPath in SQL() and the formatter #786, fix(parser): match CROSS JOIN, FULL JOIN and GROUPING SETS in any case #844, playground fix(playground): correct Analyze and Lint results from the WASM bridge #780/feat(playground): mark parse errors in the SQL editor #796, version string. Security: fix(highlight): neutralize terminal control characters in ANSI output #836, fix(mcp): pin stateless session IDs and stop logging session IDs in transport errors #835, chore(deps,test): patch certifi and markdown-it; bound testcontainer startup #837. Internal: website/CI/docs summary.
  • Updated the MCP-hardening and composite-field entries to match fix(mcp): rate-limit follow-ups from #831 review #841 and fix(parser): composite field access and table function follow-ups (#839) #843, added PR refs (feat: GoSQLX Claude Code plugin and ChatGPT app #823, feat(highlight): dialect-aware SQL syntax highlighting (API, CLI, LSP, WASM, playground) #825, fix(tokenizer): point unterminated-literal errors at the opener (byte columns, a tab is one column) #827, feat(lsp): apply the configured dialect to every language feature #828, fix(cli): derive every dialect list from keywords.DialectNames #829, fix(parser): parse composite fields and joined table functions #834), removed the duplicate LSP-legend sub-bullet and rewrote the lead paragraph, which is also the /changelog card text.
• Versions → 1.16.0: gosqlx.Version, the CLI Version (plus a "Version 1.16.0 includes" block), the cmd doc comments, the VS Code extension package.json/lock, the Claude Code plugin and marketplace, glama.json, the performance_baselines.json label, llms.txt, the website PROJECT.version badge, CLAUDE.md and examples/README. v1.15.0 shipped with these constants still at 1.14.0, so gosqlx --version, the MCP server info and /health reported 1.14.0. pygosqlx.__version__ matches pyproject (1.16.0, lockstep with GoSQLX).
• Website: split-changelog.js generated website/src/content/blog/v1-16-0.md (the same convention as v1-15-0.md). The website build also rewrote sample-ast.json (new fix(parser): composite field access and table function follow-ups (#839) #843 fields) and v1-9-1.md on main, so both regenerated files are committed here.
• Docs:
  • MIGRATION gains a v1.15.0 → v1.16.0 section with a behaviour-change checklist and companion versions.
  • ERROR_CODES: E4001 covers dialect gating, and E4002 lists the 11 dialects.
  • CLI_GUIDE: --dialect rows for format/parse/analyze/lint, and all 11 dialects in the table.
  • SQL_COMPATIBILITY: Oracle CONNECT BY/PRIOR and SQL Server PIVOT are marked parsed; BigQuery/Redshift/generic rows added.
  • api/mcp.md matches the current Config, middleware and Handler/Shutdown API.
  • api/models.md removes the nonexistent Location.Offset and documents byte columns.
  • HIGHLIGHTING has an untrusted-input note (fix(highlight): neutralize terminal control characters in ANSI output #836).
  • VS Code extension CHANGELOG gains a 1.16.0 entry.
• Merged main (fix(lsp,cli,ci): report the real version from LSP and release binaries #846, fix(cbinding): return caller-owned string from gosqlx_version; add Python CI #847, docs: v1.16.0 release follow-ups (docs nav, highlight API, LSP dialect, MCP wording) #848, feat(cbinding,python): dialect-aware exports, lint, security scan, transpile (pygosqlx 0.3.0) #850, ci(python): build pygosqlx platform wheels and publish to PyPI #851) with a normal merge commit; conflicts in docs/MIGRATION.md and vscode-extension/CHANGELOG.md keep both the v1.16.0 and v1.15.0 sections, and pygosqlx/__init__.py took main's 0.3.0 (since moved to lockstep 1.16.0, see below). CHANGELOG [1.16.0] entries added and checked against each merged diff:
  • Added: pygosqlx 1.16.0, formerly planned as 0.3.0 (dialect argument, lint, security_scan, transpile, dialects, new libgosqlx exports) (feat(cbinding,python): dialect-aware exports, lint, security scan, transpile (pygosqlx 0.3.0) #850) and prebuilt wheels with a PyPI Trusted Publishing pipeline (ci(python): build pygosqlx platform wheels and publish to PyPI #851).
  • Fixed: gosqlx_version() double free / pygosqlx version() crash (fix(cbinding): return caller-owned string from gosqlx_version; add Python CI #847); LSP serverInfo.version reports the library version, the VS Code bundled binary is stamped with the tag, CLI Version ldflag (fix(lsp,cli,ci): report the real version from LSP and release binaries #846).
  • Behavior changes: pygosqlx requires Python 3.10+ (ci(python): build pygosqlx platform wheels and publish to PyPI #851).
  • Internal: Python Bindings CI, GoReleaser tag pinning against pygosqlx-v* tags, vscode-publish version smoke test (fix(lsp,cli,ci): report the real version from LSP and release binaries #846, fix(cbinding): return caller-owned string from gosqlx_version; add Python CI #847, ci(python): build pygosqlx platform wheels and publish to PyPI #851); docs: v1.16.0 release follow-ups (docs nav, highlight API, LSP dialect, MCP wording) #848 docs pages.
  • The lead paragraph mentions pygosqlx 1.16.0; v1-16-0.md regenerated.
  • MIGRATION: companion table gains LSP serverInfo.version, libgosqlx and pygosqlx 1.16.0 rows; checklist gains LSP version, CLI ldflag, gosqlx_version() ownership and pygosqlx Python 3.10+ notes.
  • git grep 1.15.0 after the merge: remaining hits are history, the post-tag items below, or the metrics.ts benchmark release label; none belong in this PR.
• Cleanup: removes pkg/sql/parser/parser.go-e, a sed backup with conflict markers that fix(parser): accept general expressions in CONNECT BY (PRIOR as unary operator) #791 committed by accident.

Since the last review

• Merged fix(ci,python): skip floating v1 tag in release changelog; fail sdist wheel builds without libgosqlx #852 (sdist builds fail without libgosqlx; release tag lookup skips v1) and fix: single-source core lint rules, derive CLI version, fix README dialect note #853 (shared rules.CoreRules, CLI version from gosqlx.Version, tag guard, README BigQuery/Redshift wording); root.go conflict resolved to var Version = gosqlx.Version.
• Addressed the release review: date, extension changelog fix(lsp,cli,ci): report the real version from LSP and release binaries #846 entry, tight Behavior changes list, TranspileError/result types, conditional PyPI wording.
• pygosqlx now versions in lockstep with GoSQLX: 1.16.0 (from 0.2.0), published by the v1.16.0 tag; pygosqlx-v* tags remain for .postN Python-only releases.
• Replaced deprecated GoReleaser keys.

Test Plan

• After merging fix: single-source core lint rules, derive CLI version, fix README dialect note #853: task check EXIT=0 (0 lint issues); go run ./cmd/gosqlx --version → 1.16.0; pytest against a fresh libgosqlx: 184 passed, __version__ == version() == 1.16.0; website check:docs/anchors/docs-links/metrics ok

• task check (fmt, vet, golangci-lint, test:race): EXIT=0

• go run ./scripts/gen-readme-metrics --check: ok (banners still match the latest tag v1.15.0, which is intentional, see Tag-time steps)

• go run ./cmd/gosqlx --version → gosqlx version 1.16.0

• website: npm ci, npm run typecheck, npm run lint (0 errors, 7 warnings that predate this PR), npm test (34/34), npm run build, check:metrics, check:docs, check:anchors, check:docs-links, check:seo (94 pages), check:rendered

• Ran the doc examples I added: gosqlx format --dialect mysql "... LIMIT 5, 10", Oracle CONNECT BY NOCYCLE PRIOR id = mgr + 1, SQL Server PIVOT, and bigquery/generic (t).name

• JSON manifests parse

• After merging main: go build ./..., go test -race on cmd/gosqlx, pkg/lsp, pkg/gosqlx; task test:cbinding; pre-commit short suite; gen-readme-metrics --check; website check:metrics, check:docs, check:anchors, check:docs-links

Breaking Changes

None in this PR. The release itself is source-compatible (additions only) but changes runtime behaviour; see Behavior changes in the CHANGELOG and the new MIGRATION section.

Release note

This PR is the release: the notes are the CHANGELOG ## [1.16.0] section (also website/src/content/blog/v1-16-0.md).

Tag-time steps

• Release date set to 2026-10-22 (CHANGELOG, vscode-extension/CHANGELOG.md, MIGRATION heading, generated blog post)
• goreleaser check (v2.12.7): deprecated keys replaced; snapshot dry-run builds all six archives
• govulncheck (v1.1.4): only GO-2026-6809 in the local go1.27.2 stdlib; release CI uses Go 1.26 latest (1.26.10, fixed)
• PyPI pending trusted publisher (pygosqlx, ajitpratap0/GoSQLX, pygosqlx-release.yml, env pypi) and the pypi GitHub environment (tags v[0-9]*.[0-9]*.[0-9]*, pygosqlx-v*)
• Merge this PR once CI and Vercel are green, then tag v1.16.0 on main. The tag runs:
  • release.yml: tag == gosqlx.Version guard, race + cbinding tests, GoReleaser (creates the GitHub release)
  • vscode-publish.yml: 5 platform VSIXs to the Marketplace; --version smoke test must print 1.16.0
  • pygosqlx-release.yml: wheels + sdist, then pygosqlx 1.16.0 to PyPI (lockstep versioning; no separate pygosqlx tag)
  • glama-sync.yml on release publish
• Post-tag PR (fails CI before the tag exists): doc.go Version History; go run ./scripts/gen-readme-metrics; integrations/gorm and integrations/opentelemetry → go get github.com/ajitpratap0/GoSQLX@v1.16.0 && go mod tidy; @v1.15.0 install pins in docs/guides/lint-sql-in-ci.md and website/src/content/articles/lint-sql-in-ci-with-a-go-binary.md; re-measure benchmarks (metrics.json measured_at, benchmarks/compare/results/latest.json) and regenerate README / llms.txt / metrics.ts / competitor-benchmarks.json

🤖 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 22, 2026 11:17am UTC

[github-actions]

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

---

Review of PR #845: docs(release): prepare v1.16.0

I reviewed the version-constant edits, the stray-file removal and the doc and manifest changes. I did not re-run the test suite. I'm relying on the task check and website results in the PR description.

Verdict: Looks good. The changes are mechanical and low risk, and I found no blocking issues. A few small nits are below.

What checks out

• Version constants. gosqlx.Version, the CLI Version, cobra's Version: field, the cmd/gosqlx/doc.go and cmd/gosqlx/cmd/doc.go comments, glama.json, the plugin and marketplace manifests, the VS Code package.json and performance_baselines.json all say 1.16.0 and agree. This fixes the earlier case where --version, MCP server info and /health reported 1.14.0.
• Stray file. Deleting pkg/sql/parser/parser.go-e is correct. It is a sed backup containing conflict markers, and nothing can import it.
• Tag-time steps. The checklist is thorough, and the note that gen-readme-metrics --check has to wait until the tag exists is useful.

Nits and suggestions

1. Dialect count is inconsistent. The CLI docs and ERROR_CODES now list 11 dialects. These still say 8:

   • llms.txt (It supports 8 dialects (...))
   • glama.json (description lists 8 dialects)
   • the CLAUDE.md overview
   • website/src/data/metrics.ts (DIALECT_NAMES, whose comment lists 8)

   If the extra three (BigQuery, Redshift and generic) are accepted by --dialect, say so in those places too. If they are only aliases or parse targets and not full dialects, make the wording in CLI_GUIDE and ERROR_CODES clear about that. A reader will see "11" in one place and "8" in another.

2. Stale doc.go version history. The root doc.go still ends at v1.14.0 and has no v1.15.0 entry. You already plan to add v1.16.0 post-tag. Consider adding v1.15.0 in the same PR so the history has no gap.

3. Release date. The date 2026-10-21 is hard-coded in the CHANGELOG, the VS Code CHANGELOG, MIGRATION and the generated v1-16-0.md. You already flag this in the tag-time checklist. Rerunning split-changelog.js after any date change is the right way to keep them in sync.

4. CLAUDE.md. The version line is updated, but the "Requirements" and test-coverage lines are unchanged. That's fine. Note that the working tree also shows CLAUDE.md as locally modified, which is not part of this PR's diff.

5. Python. Bumping pygosqlx.__version__ to 0.2.0 to match pyproject is correct. A test asserting that __version__ equals the pyproject version would stop this drifting again.

6. Drift guard. Version drift (v1.15.0 shipped with 1.14.0 constants) happened because nothing checks it. A small CI check could compare gosqlx.Version, cmd.Version, glama.json, the plugin manifests and package.json against the latest tag or CHANGELOG heading. That could be a follow-up and doesn't need to block this PR.

Security, performance and tests

• No library behaviour changes, so no new security or performance concerns. The HIGHLIGHTING untrusted-input note (fix(highlight): neutralize terminal control characters in ANSI output #836) is a good doc addition.
• No test changes are needed for the constants. The --version smoke test in the VS Code publish workflow and the manual go run ./cmd/gosqlx --version check cover them.
  · branch docs/v1.16.0-release

[github-actions]

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

---

Review of PR #845: docs(release): prepare v1.16.0

I re-checked the code edits in the current diff: cmd/gosqlx/cmd/root.go, pkg/gosqlx/gosqlx.go and python/pygosqlx/__init__.py. I did not re-run the test suite. I'm relying on the task check and website results in the PR description.

Verdict: Looks good. The code changes are mechanical and low risk. I found no blocking issues.

Verified

• Version constants. gosqlx.Version, the CLI Version and cobra's Version: field all say 1.16.0. A grep for 1.14.0 in Go, JSON, TOML and Python files finds no stale runtime constants. The remaining hits are historical comments, doc.go history and test fixtures.
• Version block. The "Version 1.16.0 includes" and "Version 1.15.0 includes" blocks in root.go are accurate and match the CHANGELOG.
• Python. __version__ = "0.2.0" now matches pyproject.
• Stray file. Deleting parser.go-e is correct. It is a sed backup with conflict markers.
• Working tree. The only uncommitted change is the local CLAUDE.md edit, which is not part of this PR's diff.

Nits (non-blocking)

1. Dialect count. CLI_GUIDE and ERROR_CODES now say 11 dialects. CLAUDE.md, llms.txt, glama.json and DIALECT_NAMES in website/src/data/metrics.ts still say 8. If BigQuery, Redshift and generic are accepted by --dialect, either update those or say that 8 are fully supported and 3 are additional targets. Otherwise readers will see 11 in one place and 8 in another.
2. doc.go history. The root doc.go ends at v1.14.0 and has no v1.15.0 entry. Add v1.15.0 in this PR, or in the post-tag PR together with v1.16.0, so there is no gap.
3. Release date. 2026-10-21 is hard-coded in several places. Rerun split-changelog.js if the date changes, as the checklist already says.
4. Drift guard (follow-up). v1.15.0 shipped with 1.14.0 constants because nothing checks them. A CI check could compare gosqlx.Version, cmd.Version, the manifests and package.json against the latest CHANGELOG heading. A test asserting pygosqlx.__version__ equals the pyproject version would also help.

Security, performance and tests

There are no library behaviour changes, so no new security or performance concerns. No new tests are needed for the version constants. The --version smoke check in the VS Code publish workflow and your manual go run ./cmd/gosqlx --version cover them.
· branch docs/v1.16.0-release

[github-actions]

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

---

Review of PR #845: docs(release): prepare v1.16.0

I read the code diffs and grepped for leftover version strings. I did not re-run the test suite. I'm relying on the task check and website results in the PR description.

Verdict: Looks good. I found no blocking issues.

Verified

• Version constants. gosqlx.Version, the CLI Version and cobra's Version: field all say 1.16.0. A grep of Go, JSON, TOML and Python files finds no stale 1.14.0 runtime constants. The remaining hits are historical comments and test fixtures.
• root.go version block. The new "Version 1.16.0 includes" block and the added "Version 1.15.0 includes" block are comment-only. They match the CHANGELOG themes.
• Python. __version__ = "0.2.0" now matches pyproject.
• Stray file. Deleting pkg/sql/parser/parser.go-e is correct. It is a sed backup with conflict markers, and nothing can import it.
• doc.go. The root doc.go does have a v1.15.0 entry (line 290). One earlier review comment said it was missing, and that was wrong. Only the v1.16.0 line is outstanding, and your post-tag checklist already covers it.

Nits (non-blocking)

1. Dialect count. root.go says "11 dialect names everywhere", and CLI_GUIDE and ERROR_CODES now list 11. CLAUDE.md, llms.txt, glama.json and DIALECT_NAMES in website/src/data/metrics.ts still describe 8. If BigQuery, Redshift and generic are accepted by --dialect but aren't fully supported dialects, say so, for example "8 fully supported, 11 accepted by --dialect". Otherwise readers will see 11 in one place and 8 in another.
2. Release date. 2026-10-21 is hard-coded in several places (the CHANGELOG, the VS Code CHANGELOG, MIGRATION and the generated v1-16-0.md). The tag-time checklist already covers this. Rerun split-changelog.js if the date changes.
3. Drift guard (follow-up). v1.15.0 shipped with 1.14.0 constants because nothing checks them. A small CI check could compare gosqlx.Version, cmd.Version, the plugin manifests, glama.json and package.json against the latest CHANGELOG heading. A test asserting that pygosqlx.__version__ equals the pyproject version would also help.
4. CLAUDE.md. The working tree shows a local CLAUDE.md modification that isn't part of this PR's diff, so check it before tagging.

Security, performance and tests

• There are no library behaviour changes, so no new security or performance concerns. The HIGHLIGHTING untrusted-input note (fix(highlight): neutralize terminal control characters in ANSI output #836) is a good addition.
• No new tests are needed for the version constants. The --version smoke test in the VS Code publish workflow and your manual go run ./cmd/gosqlx --version check cover them.
  · branch docs/v1.16.0-release

[github-actions]

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

---

Review of PR #845: docs(release): prepare v1.16.0

I checked the version constants, the stray-file deletion and the dialect wording by grep. I did not re-run the test suite. I'm relying on the task check and website results in the PR description.

Verdict: Looks good. I found no blocking issues. The changes are mechanical and don't touch library behaviour.

Verified

• gosqlx.Version is 1.16.0 (pkg/gosqlx/gosqlx.go:33). The grep for leftover 1.14.0 strings in non-test Go, JSON, Python and TOML files finds only historical comments: pool_statement_release.go, the doc.go history and the root.go "Version 1.14.0 includes" block.
• Deleting pkg/sql/parser/parser.go-e is correct. It is a sed backup containing conflict markers.
• The root doc.go has v1.14.0 and v1.15.0 history entries. Only the v1.16.0 line is outstanding, and your post-tag checklist already covers it.

Nits (non-blocking)

1. Dialect count is inconsistent. CLI_GUIDE and ERROR_CODES now list 11 dialects. These places still say 8:

   • llms.txt:5
   • CLAUDE.md:15
   • glama.json
   • DIALECT_NAMES in website/src/data/metrics.ts

   If BigQuery, Redshift and generic are only accepted by --dialect and aren't fully supported dialects, say "8 supported, 11 accepted by --dialect". Otherwise update all of them.

2. CLAUDE.md local modification. The working tree has an uncommitted CLAUDE.md change that reverts the version line from current: v1.16.0 to current: v1.14.0. The PR's committed version is the correct one. Don't commit the local edit, or the PR will regress the version.

3. Release date. 2026-10-21 is hard-coded in several places. The tag-time checklist already says to rerun split-changelog.js if it changes.

4. Drift guard (follow-up). v1.15.0 shipped with 1.14.0 constants because nothing checks them. A small CI check could compare gosqlx.Version, the CLI Version, the plugin manifests, glama.json and package.json against the latest CHANGELOG heading. A test asserting that pygosqlx.__version__ equals the pyproject version would also help.

Security, performance and tests

There are no library behaviour changes, so no new security or performance concerns. The HIGHLIGHTING untrusted-input note (#836) is a good addition. No new tests are needed for the version constants. The --version smoke test in the VS Code publish workflow and your manual go run ./cmd/gosqlx --version check cover them.
· branch docs/v1.16.0-release

[github-actions]

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

---

Review of PR #845: docs(release): prepare v1.16.0

I checked the version constants, the Python version change, the stray-file deletion and the local working tree. I did not re-run the test suite and rely on the task check and website results in the description.

Verdict: Looks good. The one thing to fix before tagging is a stale PR description (item 1).

Verified

• gosqlx.Version is 1.16.0 (pkg/gosqlx/gosqlx.go:33). The CLI Version derives from it (cmd/gosqlx/cmd/root.go:60), so the two can't drift again.
• python/pyproject.toml and pygosqlx.__version__ are both 1.16.0. test_version_in_lockstep_with_library asserts that __version__ equals the library version(), so it guards the Python side against drift. That covers the guard I suggested earlier.
• Deleting pkg/sql/parser/parser.go-e is correct. It is a sed backup containing conflict markers.

Issues and nits

1. The PR description is stale on pygosqlx versioning. Commit 7d86230 moved pygosqlx to lockstep versioning (1.16.0). The description still says "0.3.0 after the main merge", "pygosqlx 0.3.0" in the CHANGELOG, MIGRATION and lead-paragraph notes, and the tag-time step "push tag pygosqlx-v0.3.0".
   • Following that checklist would tag the wrong version.
   • Please check CHANGELOG.md, docs/MIGRATION.md, python/README.md, website/src/content/blog/v1-16-0.md and .github/workflows/pygosqlx-release.yml for leftover "0.3.0" references, and align the tag name in the checklist with what the release workflow expects.
2. Dialect count is inconsistent. CLI_GUIDE and ERROR_CODES list 11 dialects. CLAUDE.md:15, llms.txt:5, glama.json and DIALECT_NAMES in website/src/data/metrics.ts still say 8. If BigQuery, Redshift and generic are only accepted by --dialect, say "8 supported, 11 accepted by --dialect". Otherwise update all of them.
3. Local CLAUDE.md edit. The working tree has an uncommitted change that reverts current: v1.16.0 to current: v1.14.0. The committed version is correct. Don't commit the local edit.
4. Release date. 2026-10-21 is hard-coded in the CHANGELOG, the VS Code CHANGELOG, MIGRATION and v1-16-0.md. Today is 2026-10-22, so confirm the date at tag time and rerun split-changelog.js if it changes.
5. Drift guard (follow-up). v1.15.0 shipped with 1.14.0 constants. A small CI check could compare the manifests (glama.json, plugin and marketplace JSON, package.json) against gosqlx.Version. That would extend the guard beyond Python and can be a separate PR.

Security, performance and tests

There are no library behaviour changes, so no new security or performance concerns. The HIGHLIGHTING untrusted-input note (#836) is a good addition. No new tests are needed for the constants.
· branch docs/v1.16.0-release