Skip to content

feat: API specs update for version latest#58

Merged
ChiragAgg5k merged 1 commit intomainfrom
feat-latest-specs
May 4, 2026
Merged

feat: API specs update for version latest#58
ChiragAgg5k merged 1 commit intomainfrom
feat-latest-specs

Conversation

@appwrite-specs
Copy link
Copy Markdown

@appwrite-specs appwrite-specs Bot commented May 4, 2026

This PR contains API specification updates for version latest.

@ChiragAgg5k ChiragAgg5k merged commit a670172 into main May 4, 2026
2 checks passed
@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented May 4, 2026

Greptile Summary

This automated PR bumps all six API specs from v1.9.2 to v1.9.3. The headline additions are three new OAuth2 providers (fusionauth, keycloak, kick), a refactor from a single generic projectsUpdateOAuth2 endpoint to per-provider update endpoints, and a suite of new management endpoints (mock phones, ephemeral keys, policies, email templates, manager blocks).

  • projectsCreateJWT (POST /projects/{projectId}/jwts) has been removed from both console specs with no replacement, which is a breaking change for any consumer of the console API that creates scoped project JWTs.
  • Five console operations changed their operationId prefix from projects (plural) to project (singular) — e.g. projectsDeleteprojectDelete, projectsUpdateAuthStatusprojectUpdateAuthMethod — which will break SDK codegen against the old operation IDs.

Confidence Score: 4/5

Safe to merge pending confirmation that the projectsCreateJWT removal and operationId renames are intentional breaking changes in v1.9.3.

One P1 finding (removal of projectsCreateJWT with no replacement) and one P2 (operationId renames that may break existing SDK codegen). All other changes are additive and consistent across both OpenAPI3 and Swagger2 formats.

specs/latest/open-api3-latest-console.json and specs/latest/swagger2-latest-console.json carry the breaking operationId removals and renames.

Important Files Changed

Filename Overview
specs/latest/open-api3-latest-console.json Largest changeset; version bump 1.9.2 to 1.9.3; removes projectsCreateJWT with no replacement; renames projectsDelete to projectDelete; replaces generic projectsUpdateOAuth2 with per-provider endpoints; adds mock phone CRUD, ephemeral keys, policies, and email templates listing.
specs/latest/open-api3-latest-server.json Version bump 1.9.2 to 1.9.3; adds new OAuth2 providers (fusionauth, keycloak, kick); replaces generic projectsUpdateOAuth2 with per-provider endpoints; adds mock phone, ephemeral key, policy, and email-template endpoints.
specs/latest/open-api3-latest-client.json Version bump 1.9.2 to 1.9.3; adds fusionauth, keycloak, and kick as new OAuth2 providers; weight reordering for MFA/avatar endpoints.
specs/latest/swagger2-latest-console.json Swagger2 mirror of open-api3-latest-console.json changes; same five operations removed without direct replacement, including projectsCreateJWT.
specs/latest/swagger2-latest-server.json Swagger2 mirror of open-api3-latest-server.json changes; consistent with OpenAPI3 counterpart.
specs/latest/swagger2-latest-client.json Swagger2 mirror of open-api3-latest-client.json changes; consistent version bump and new OAuth2 provider additions.

Comments Outside Diff (2)

  1. specs/latest/open-api3-latest-console.json, line 1 (link)

    P1 projectsCreateJWT endpoint removed with no replacement

    The POST /projects/{projectId}/jwts endpoint (operationId: projectsCreateJWT) has been dropped from both the OpenAPI3 and Swagger2 console specs without any replacement operation. This was the only way to create a scoped, short-lived JWT token for a project via the console API. Any SDK codegen or console tooling that calls this endpoint will break silently. The same removal is present in swagger2-latest-console.json.

  2. specs/latest/open-api3-latest-console.json, line 1 (link)

    P2 projectsUpdateAuthStatus and projectsUpdateMockNumbers removed without exact replacement

    Both projectsUpdateAuthStatus and projectsUpdateMockNumbers have been removed from the console spec. projectsUpdateAuthStatus appears to be superseded by the new projectUpdateAuthMethod, and projectsUpdateMockNumbers by the new mock-phone CRUD suite — but the naming prefix changed from plural (projects) to singular (project). If any generated SDK or internal tool references the old operation IDs directly, those calls will fail. The same pattern is present in swagger2-latest-console.json.

Reviews (1): Last reviewed commit: "chore: update API specs and SDK examples" | Re-trigger Greptile

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.

1 participant