Skip to content

chore: upgrade to appwrite sdk-for-go v6 (6.0.0)#33

Merged
levivannoort merged 3 commits into
mainfrom
chore/sdk-v6
Jul 17, 2026
Merged

chore: upgrade to appwrite sdk-for-go v6 (6.0.0)#33
levivannoort merged 3 commits into
mainfrom
chore/sdk-v6

Conversation

@levivannoort

Copy link
Copy Markdown
Member

Summary

Upgrades the Appwrite Go SDK from v5 to v6.0.0 across the whole provider.

  • github.com/appwrite/sdk-for-go/v5 v5.1.0.../v6 v6.0.0
  • Updated all import paths in the provider, common helpers, and every service.
  • Bumped the Go toolchain to match.

Import-path-only change; go build ./... passes.

🤖 Generated with Claude Code

Bump github.com/appwrite/sdk-for-go from v5 to v6.0.0 across all
services and the provider, and bump the Go toolchain accordingly.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@greptile-apps

greptile-apps Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR upgrades the Appwrite Go SDK dependency across the entire provider from sdk-for-go/v5 v5.1.0 to sdk-for-go/v6 v6.0.0, updating all 32 import paths and the Go toolchain version.

  • All service files (backup, bucket, column, database, file, function, provider, row, site, subscriber, table, team, topic, user, webhook) have their imports mechanically updated from /v5 to /v6.
  • column/resource.go intentionally retains the now-deprecated CreateStringColumn and UpdateStringColumn calls (suppressed with //nolint:staticcheck) because the replacement TextColumn API lacks a size parameter; explanatory comments are included at both call sites.
  • go.mod and go.sum are updated consistently with matching checksums for the new module path.

Confidence Score: 5/5

Safe to merge — all changes are mechanical import-path updates with one well-justified and commented exception in the column resource.

The upgrade touches 32 files but every change is a one-line import path substitution from /v5 to /v6. The single substantive deviation — keeping the deprecated CreateStringColumn/UpdateStringColumn calls — is explicitly documented and suppressed at both sites, with a clear migration path noted. No logic, data flow, or API surface was altered beyond what the SDK version upgrade requires.

No files require special attention. internal/services/column/resource.go warrants a follow-up once the upstream SDK's TextColumn gains a size parameter, but it is handled correctly for now.

Important Files Changed

Filename Overview
go.mod SDK dependency bumped from sdk-for-go/v5 v5.1.0 to v6 v6.0.0; Go toolchain bumped from 1.25.0 to 1.26.5
go.sum Checksum entries replaced for the new sdk-for-go/v6 module; all other checksums unchanged
internal/services/column/resource.go Import path updated to v6; CreateStringColumn and UpdateStringColumn intentionally kept despite deprecation (TextColumn lacks size parameter), with explanatory comments and nolint directives
internal/common/helpers.go Import paths updated from sdk-for-go/v5 to v6; no functional changes
internal/provider/provider.go Import paths updated from sdk-for-go/v5 to v6; no functional changes
internal/services/backup/resource.go Import paths updated to sdk-for-go/v6; no functional changes
internal/services/function/deployment_resource.go Import paths updated to sdk-for-go/v6; no functional changes
internal/services/site/deployment_resource.go Import paths updated to sdk-for-go/v6; no functional changes

Reviews (2): Last reviewed commit: "chore: drop ponytail prefix from lint co..." | Re-trigger Greptile

levivannoort and others added 2 commits July 14, 2026 20:50
CreateStringColumn/UpdateStringColumn are deprecated in SDK v6 in favor
of TextColumn, but TextColumn has no size option. Keep StringColumn to
honor `size` and suppress SA1019.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@levivannoort
levivannoort merged commit f9d856f into main Jul 17, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants