[srstack]

Release

• Tag: v0.2.10 (patch; there is no source version constant or go.mod version to bump)
• Notes: docs/release-notes/v0.2.10.md — the release workflow requires this file and passes it to GoReleaser
• Merging this PR does not publish anything; the tag push does

Changes included (v0.2.9..main)

PR	Change
#74	ti fs copy-file enforces the no-overwrite contract on companion uploads (fixes #72)
#75	ti fs list-files / find-files / search-file-content keep spaces in names and paths (fixes #73)
#76	Adds the azure-centralus Filesystem placement; azure-centralus and gcp-us-east1 are Filesystem-only for Starter placement validation

Validation

• make test
• make e2e
• make release-snapshot (GoReleaser v2.18.3) — five platform archives and ti_checksums.txt produced; the snapshot binary reports ti 0.2.10-next and the Linux archive contains README.md and ti
• make live-e2e with the real companion — needs the live-e2e profile and cloud credentials; please run this before publishing

Drive9 companion

Prepared against the published build d39a6d1 (git_hash d39a6d1b3ba1d3e23fc75b8d530259c861855702, built 2026-10-08). https://releases.drive9.ai/latest/SHA256SUMS and https://drive9.ai/releases/checksums.txt agree on all five ti targets:

Artifact	SHA-256
drive9-darwin-amd64	5f33ba5937eb4771fb9109529706413f4bb3c501f4f673e0be9a8b5a0874f811
drive9-darwin-arm64	84c53cf948eb7a1b5cd8aeb2484bbcf4d81018b0fcbe5b7ffa4d55a39e2eb1c1
drive9-linux-amd64	e8b8c7245c46e855fd37eaf6e05386d6fc492b51ecc4b40686ffd81de304378d
drive9-linux-arm64	275c83194cd28ed75b2b4d1a9071df8ca86583a03248322f4567579710235e28
drive9-windows-amd64.exe	e2df1caec1b806f26096bf9763d4f87209708772eb23a262e5041823a603a7f9

The checksum-verified drive9-linux-amd64 artifact matches the manifest and exposes the required surface: drive9 fs layer includes fork, chain, and delete, and drive9 mount accepts -layer and -checkpoint. These endpoints are mutable, so recheck the manifests before publishing.

Publish after merge

From a clean checkout of the merged commit:

git fetch origin --tags && git switch main && git pull --ff-only origin main
git status --short && git log -1 --oneline
git show HEAD:docs/release-notes/v0.2.10.md
git tag -a v0.2.10 -m "Release v0.2.10"
git push origin refs/tags/v0.2.10
gh run watch "$(gh run list --repo tidbcloud/ti-cli --workflow release.yml --limit 1 --json databaseId --jq '.[0].databaseId')" --repo tidbcloud/ti-cli --exit-status

Do not move the tag afterwards. The release workflow checks that the notes file exists and runs GoReleaser; it does not run tests.

Parallel work

The published regions page in docs/pingcap-docs/docs (ai/ti/reference/ti-regions-security-and-limitations.md) still lists neither GCP nor Azure. It lives in the separate pingcap/docs repository, so it is not part of this PR.

[Copilot]

🟢 Approval recommended

It only adds a correctly named release-notes file whose factual claims (flags, error messages, endpoints, region classification) all verify against the current code, with no product-code changes.

0 open findings

What changed in this PR

This PR prepares the v0.2.10 patch release by adding the required release-notes file docs/release-notes/v0.2.10.md. The release workflow (.github/workflows/release.yml) requires a notes file named exactly for the tag and passes it to GoReleaser, so this file is a prerequisite for publishing. No product code is changed; the user-facing behavior it documents (PRs #74, #75, #76) already landed on main.

Changes:

• Adds v0.2.10 release notes summarizing the new azure-centralus Filesystem placement, the Filesystem-only Starter validation for azure-centralus/gcp-us-east1, and two ti fs data-plane bug fixes.
• Documents upgrade/install steps and the Drive9 companion build (d39a6d1) with per-artifact SHA-256 checksums.

File	Description
docs/​release-notes/​v0.2.10.md	New release-notes file required by the release workflow; documents v0.2.10 features, bug fixes, upgrade instructions, and the companion build.

Verification notes (all confirmed accurate):

• Configure flags (--region-code, --tidb-cloud-public-key, --tidb-cloud-private-key, --non-interactive) match internal/cli/commands.go.
• The fs.target_exists message and the Starter Filesystem-only rejection message match internal/fs/data.go:678 and internal/config/region/region.go:187.
• The azure-centralus endpoint (https://azure-centralus.drive9.ai) and the filesystem-only classification of azure-centralus/gcp-us-east1 match internal/api/endpoints/endpoints.go and internal/config/region/region.go; ti configure accepts these codes via ParsePlacementCode.
• The filename matches the workflow's expected path docs/release-notes/v0.2.10.md, and the format is consistent with prior notes (v0.2.9.md). No spelling, grammar, or future-date issues.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.