Release v0.3.2

[thomasp85]

Target version: v0.3.2

Previous release: v0.3.1

1. Pre-release verification

• main is green on the Main Extension Distribution Pipeline + Code Quality Check
• Locally on the commit being released: make and GGSQL_NO_OPEN_BROWSER=1 make test pass
• No outstanding TODO(ggsql-*) markers tied to a transitional dependency that should be resolved before the tag
• If the DuckDB target version is changing, all four refs are in sync:
  • .github/workflows/MainDistributionPipeline.yml — duckdb_version, ci_tools_version, and the @vX.Y.Z workflow refs
  • duckdb/ submodule pinned to the matching DuckDB tag
  • extension-ci-tools/ submodule pinned to the matching tag
• Release notes drafted, summarising user-visible changes since v0.3.1. gh release create --generate-notes is fine for an autogenerated baseline; tighten by hand.

2. Tag and publish the GitHub Release

• Tag the commit:

  git tag -a v0.3.2 -m "v0.3.2"
  git push origin v0.3.2
  

• Wait for Main Extension Distribution Pipeline to finish green on the tag (built artifacts are needed for the next step)
• Publish the GitHub Release from the tag with the notes drafted above:

  gh release create v0.3.2 --title "v0.3.2" --notes-file RELEASE_NOTES.md
  

  (or via the GitHub UI)

3. Submit to duckdb/community-extensions

The community-extensions repo is the entrypoint for INSTALL ggsql FROM community. Their CI builds, signs, and publishes the binaries to community-extensions.duckdb.org once the PR merges.

• Resolve the commit SHA the tag points at:

  git rev-list -n 1 v0.3.2
  

• In the posit-dev/community-extensions fork, sync main with upstream duckdb/community-extensions:

  gh repo sync posit-dev/community-extensions -b main
  

• Copy this repo's community-extension.yml to extensions/ggsql/description.yml in the fork (overwrite any existing copy)
• Edit the copied file:
  • extension.version: 0.3.2 (no leading v)
  • repo.ref: <full SHA from above>
• Open a PR against duckdb/community-extensions:
  • Title: ggsql: v0.3.2
  • Body links: GitHub Release URL + tagged-commit URL
• Address any review feedback. Watch the PR's CI — failures usually point at a missing platform exclusion, build flag, or descriptor field.

4. Post-merge verification

• In a fresh DuckDB shell on macOS or Linux:

  INSTALL ggsql FROM community;
  LOAD ggsql;
  SELECT ggsql('SELECT 1 AS x, 2 AS y VISUALISE x, y DRAW point');

  Expect a plot URL.
• Repeat on Windows if a runner is available — the mingw target is the most regression-prone platform.
• Close this issue and link the merged community-extensions PR in the closing comment.