fix: use curated release notes

Author: Icemap

.github/workflows/release.yml

@@ -22,11 +22,19 @@ jobs:
         with:
           go-version-file: go.mod
 
+      - name: Check release notes
+        run: |
+          notes="docs/release-notes/${GITHUB_REF_NAME}.md"
+          if [ ! -f "$notes" ]; then
+            echo "::error::Missing release notes file: $notes"
+            exit 1
+          fi
+
       - name: Run GoReleaser
         uses: goreleaser/goreleaser-action@v7
         with:
           distribution: goreleaser
           version: "~> v2"
-          args: release --clean
+          args: release --clean --release-notes=docs/release-notes/${{ github.ref_name }}.md
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

README.md

@@ -80,6 +80,8 @@ Build local release artifacts without publishing:
 make release-snapshot
 ```
 
+Release publishing uses GoReleaser and GitHub Releases. Before pushing a `v*` tag, write a summary-style release note at `docs/release-notes/<tag>.md`, for example `docs/release-notes/v0.1.0.md`. The release workflow passes that file to GoReleaser with `--release-notes`, and fails when the tag-specific file is missing so GitHub Releases do not fall back to a commit-list changelog.
+
 Run the live TiDB Cloud e2e entrypoint:
 
 ```bash

docs/release-notes/v0.1.0.md

@@ -0,0 +1,67 @@
+# tdc v0.1.0
+
+This is the first MVP preview of `tdc`, an agent-friendly CLI for TiDB Cloud Starter and tdc fs workflows. It provides a scriptable command surface for configuring local credentials, managing Starter clusters, preparing SQL access roles, operating tdc fs resources, mounting remote filesystems, and using filesystem-backed Git, journal, and vault workflows.
+
+## What You Can Do
+
+Configure a local profile with a canonical region code:
+
+```bash
+tdc configure
+TDC_REGION_CODE=aws-us-east-1 \
+TDC_PUBLIC_KEY="$TDC_PUBLIC_KEY" \
+TDC_PRIVATE_KEY="$TDC_PRIVATE_KEY" \
+tdc configure --non-interactive
+```
+
+Manage TiDB Cloud Starter resources from the CLI:
+
+```bash
+tdc organization list-projects
+tdc db create-db-cluster --db-cluster-name demo --db-cluster-type starter --project-id <project-id>
+tdc db list-db-clusters
+tdc db describe-db-cluster --db-cluster-id <cluster-id>
+tdc db update-db-cluster --db-cluster-id <cluster-id> --db-cluster-name demo-renamed
+tdc db delete-db-cluster --db-cluster-id <cluster-id>
+```
+
+Prepare database users for query access and run SQL through the HTTPS SQL API. The default role is read-write, and read-only/admin access must be selected explicitly:
+
+```bash
+tdc db create-db-sql-users --db-cluster-id <cluster-id>
+tdc db execute-sql-statement --db-cluster-id <cluster-id> --sql "select 1"
+tdc db execute-sql-statement --db-cluster-id <cluster-id> --read-only --sql "select 1"
+tdc db format-db-connection-string --db-cluster-id <cluster-id> --format mysql-uri
+tdc db format-db-connection-string --db-cluster-id <cluster-id> --read-only --format env
+```
+
+Create and operate a tdc fs resource, then use either data-plane commands or a local mount:
+
+```bash
+tdc fs create-file-system --file-system-name workspace
+tdc fs check-file-system
+tdc fs cp --from-local ./notes.md --to-remote /notes.md --overwrite
+tdc fs cat --path /notes.md
+tdc fs ls --path /
+tdc fs mount-file-system --mount-path /tmp/tdc-workspace
+tdc fs unmount-file-system --mount-path /tmp/tdc-workspace
+```
+
+Use filesystem-adjacent workflows when a tdc fs resource is configured:
+
+```bash
+tdc fs-git add-git-worktree --base-path /workspace --worktree-path /workspace-feature
+tdc fs-journal create-journal
+tdc fs-journal append-journal-entries --journal-id <journal-id> --entry-json '{"event":"demo"}'
+tdc fs-vault create-secret --secret-name app --field password=secret
+```
+
+Install and update from GitHub Releases:
+
+```bash
+curl -fsSL https://github.com/tidbcloud/tdc/releases/latest/download/install.sh | sh -s -- --yes
+tdc cli check-update
+tdc cli update --yes
+```
+
+The release also includes structured JSON/text output, JMESPath `--query`, shared `--dry-run` behavior for mutating control-plane commands, CI workflows, and a live e2e suite that verifies real TiDB Cloud and tdc fs flows.