Skip to content

feat: SDK update for version 26.1.0#68

Merged
ChiragAgg5k merged 6 commits into
mainfrom
dev
Jul 24, 2026
Merged

feat: SDK update for version 26.1.0#68
ChiragAgg5k merged 6 commits into
mainfrom
dev

Conversation

@ChiragAgg5k

@ChiragAgg5k ChiragAgg5k commented Jul 23, 2026

Copy link
Copy Markdown
Member

This PR contains updates to the SDK for version 26.1.0.

What's Changed

  • Added: Apps service for managing OAuth2 applications, keys, and installations
  • Added: OAuth2 service with authorize, grant, device authorization, and consent flows
  • Added: account OAuth2 consent methods list_consents, get_consent, delete_consent, and consent token methods
  • Added: app installation management methods to Organization and Teams services
  • Added: installation_access_token_duration parameter to project.update_o_auth2_server
  • Added: token parameter to sites.get_deployment_download
  • Added: oauth2.introspect and organization installation key scopes

@ChiragAgg5k ChiragAgg5k changed the title feat: Ruby SDK update for version 26.1.0 feat: SDK update for version 26.1.0 Jul 23, 2026
@greptile-apps

greptile-apps Bot commented Jul 23, 2026

Copy link
Copy Markdown

Greptile Summary

Updates the Ruby SDK to version 26.1.0.

  • Adds Apps and OAuth2 services, models, documentation, and public requires.
  • Adds account consent and organization/team installation APIs.
  • Expands dedicated database and TablesDB capabilities.
  • Updates project OAuth2 settings, deployment downloads, enums, models, and release metadata.
  • Updates pinned publishing workflow actions.

Confidence Score: 5/5

The PR appears safe to merge based on this follow-up review.

No new blocking failure eligible for this follow-up remains.

Important Files Changed

Filename Overview
lib/appwrite/models/database.rb Corrects the failover status constant reference identified in the previous review.
lib/appwrite/services/backups.rb Updates restoration request parameters and documentation; the previously reported compatibility concern remains unchanged and is not repeated in this follow-up.
lib/appwrite/models/database_status_volume.rb Adds the database status volume model; the previously reported field-naming concern remains unchanged and is not repeated in this follow-up.
lib/appwrite/services/apps.rb Introduces the Apps service for application, credential, scope, and installation management.
lib/appwrite/services/oauth2.rb Introduces OAuth2 authorization, grant, token, consent, project, and organization operations.
lib/appwrite/services/tables_db.rb Adds database status, replica, specification, and failover operations.
lib/appwrite.rb Exposes the newly generated services and models through the package entry point.

Reviews (2): Last reviewed commit: "chore: update Ruby SDK to 26.1.0" | Re-trigger Greptile

Comment thread lib/appwrite/models/database.rb Outdated
#
# @return [BackupRestoration]
def create_restoration(archive_id:, services:, new_resource_id: nil, new_resource_name: nil, new_specification: nil)
def create_restoration(archive_id:, services:, new_resource_id: nil, new_resource_name: nil)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Restoration keyword compatibility broken

When code written against 26.0.0 passes the documented new_specification: keyword, this reduced signature raises ArgumentError: unknown keyword: :new_specification before sending the restoration request. Retain compatibility or release and document this as a breaking API change.

Prompt To Fix With AI
This is a comment left during a code review.
Path: lib/appwrite/services/backups.rb
Line: 351

Comment:
**Restoration keyword compatibility broken**

When code written against 26.0.0 passes the documented `new_specification:` keyword, this reduced signature raises `ArgumentError: unknown keyword: :new_specification` before sending the restoration request. Retain compatibility or release and document this as a breaking API change.

How can I resolve this? If you propose a fix, please make it concise.

Fix in Claude Code Fix in Codex


def self.from(map:)
DatabaseStatusVolume.new(
xpath: map["path"],

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Volume path exposed as xpath

The API's path field is assigned to the model's xpath attribute, forcing SDK consumers to use an unrelated public name for the volume path. Rename the initializer, reader, and backing variable to path so the Ruby model matches its serialized field.

Prompt To Fix With AI
This is a comment left during a code review.
Path: lib/appwrite/models/database_status_volume.rb
Line: 25

Comment:
**Volume path exposed as xpath**

The API's `path` field is assigned to the model's `xpath` attribute, forcing SDK consumers to use an unrelated public name for the volume path. Rename the initializer, reader, and backing variable to `path` so the Ruby model matches its serialized field.

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Fix in Claude Code Fix in Codex

@ChiragAgg5k ChiragAgg5k changed the title feat: SDK update for version 26.1.0 feat: Ruby SDK update for version 26.1.0 Jul 23, 2026
@ChiragAgg5k ChiragAgg5k changed the title feat: Ruby SDK update for version 26.1.0 feat: SDK update for version 26.1.0 Jul 23, 2026
@ChiragAgg5k
ChiragAgg5k merged commit 109f7f7 into main Jul 24, 2026
1 check 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