Skip to content

chore: bump SDK version to 4.2.0#96

Merged
TorstenDittmann merged 1 commit into
mainfrom
concurrent-chunk-uploads-version-bump-1-9-x
May 21, 2026
Merged

chore: bump SDK version to 4.2.0#96
TorstenDittmann merged 1 commit into
mainfrom
concurrent-chunk-uploads-version-bump-1-9-x

Conversation

@TorstenDittmann

Copy link
Copy Markdown
Contributor

This PR bumps SDK version metadata to 4.2.0 after the concurrent chunk upload update.

@greptile-apps

greptile-apps Bot commented May 21, 2026

Copy link
Copy Markdown

Greptile Summary

Bumps the SDK version from 4.1.0 to 4.2.0 across all relevant files, following the concurrent chunk upload feature update.

  • Appwrite.csproj: NuGet package version updated to 4.2.0.
  • Client.cs: Both the user-agent header string and x-sdk-version header updated to 4.2.0.
  • README.md: All three installation code examples updated to reference 4.2.0.

Confidence Score: 5/5

This is a straightforward version string update with no logic changes — safe to merge.

All three files only change version literals from 4.1.0 to 4.2.0, with no behavioural or functional modifications. The changes are consistent across the package metadata, runtime headers, and documentation.

No files require special attention.

Important Files Changed

Filename Overview
Appwrite/Appwrite.csproj Version bumped from 4.1.0 to 4.2.0 in the NuGet package metadata
Appwrite/Client.cs User-Agent string and x-sdk-version header updated from 4.1.0 to 4.2.0
README.md Installation instructions updated to reference version 4.2.0 in all three code examples

Reviews (1): Last reviewed commit: "chore: bump SDK version to 4.2.0" | Re-trigger Greptile

@TorstenDittmann TorstenDittmann merged commit 5591490 into main May 21, 2026
2 checks passed
@TorstenDittmann TorstenDittmann deleted the concurrent-chunk-uploads-version-bump-1-9-x branch May 21, 2026 18:57
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