chore: update Command Line SDK to 24.0.0 (#347)

Author: ChiragAgg5k

.github/workflows/publish.yml

@@ -226,15 +226,12 @@ jobs:
             echo "formula_path=${FORMULA_PATH}"
           } >> "$GITHUB_OUTPUT"
 
-      - name: Open pull request on Homebrew tap
+      - name: Commit Homebrew formula update
         working-directory: homebrew-tap
         env:
           RELEASE_TAG: ${{ github.event.release.tag_name }}
           EXECUTABLE_NAME: ${{ steps.tap.outputs.executable }}
           FORMULA_PATH: ${{ steps.tap.outputs.formula_path }}
-          SOURCE_REPO: ${{ github.repository }}
-          SERVER_URL: ${{ github.server_url }}
-          GH_TOKEN: ${{ steps.bot-token.outputs.token }}
         run: |
           set -euo pipefail
 
@@ -243,27 +240,12 @@ jobs:
             exit 0
           fi
 
-          BASE_BRANCH="$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')"
-          BRANCH="release/${EXECUTABLE_NAME}-${RELEASE_TAG}"
-
           git config user.name "appwrite-bot[bot]"
           git config user.email "217594562+appwrite-bot[bot]@users.noreply.github.com"
 
-          git checkout -B "$BRANCH"
           git add "$FORMULA_PATH"
           git commit -m "${EXECUTABLE_NAME} ${RELEASE_TAG}"
-          git push -f -u origin "$BRANCH"
-
-          PR_TITLE="${EXECUTABLE_NAME} ${RELEASE_TAG}"
-          PR_BODY=$(printf 'Automated formula update for the `%s` CLI release [`%s`](%s/%s/releases/tag/%s).\n\nOpened automatically by the `%s` publish workflow after release binaries were uploaded.' "$EXECUTABLE_NAME" "$RELEASE_TAG" "$SERVER_URL" "$SOURCE_REPO" "$RELEASE_TAG" "${SOURCE_REPO#*/}")
 
-          EXISTING_PR="$(gh pr list --head "$BRANCH" --state open --json number --jq '.[0].number' || true)"
-          if [ -n "$EXISTING_PR" ]; then
-            gh pr edit "$EXISTING_PR" --title "$PR_TITLE" --body "$PR_BODY"
-          else
-            gh pr create \
-              --title "$PR_TITLE" \
-              --body "$PR_BODY" \
-              --base "$BASE_BRANCH" \
-              --head "$BRANCH"
-          fi
+          BRANCH="$(git rev-parse --abbrev-ref HEAD)"
+          git pull --rebase origin "$BRANCH"
+          git push origin "HEAD:${BRANCH}"

CHANGELOG.md

@@ -1,5 +1,11 @@
 # Change Log
 
+## 24.0.0
+
+* Added: `login` against Cloud now signs in through your browser
+* Updated: `--email`, `--password`, `--mfa`, and `--code` now apply to self-hosted instances only
+* Updated: Existing Cloud sessions keep working in read-only mode until you run `login` again
+
 ## 23.2.0
 
 * Added: `apps` installation commands: `list-installations`, `get-installation`, `delete-installation`, `create-installation-token`

README.md

@@ -29,7 +29,7 @@ Once the installation is complete, you can verify the install using
 
 ```sh
 $ appwrite -v
-23.2.0
+24.0.0
 ```
 
 ### Install using prebuilt binaries
@@ -83,7 +83,7 @@ $ scoop install https://raw.githubusercontent.com/appwrite/sdk-for-cli/master/sc
 Once the installation completes, you can verify your install using
 ```
 $ appwrite -v
-23.2.0
+24.0.0
 ```
 
 ## Getting Started 

bun.lock

@@ -13,8 +13,8 @@
 # You can use "View source" of this page to see the full script.
 
 # REPO
-$GITHUB_x64_URL = "https://github.com/appwrite/sdk-for-cli/releases/download/23.2.0/appwrite-cli-win-x64.exe"
-$GITHUB_arm64_URL = "https://github.com/appwrite/sdk-for-cli/releases/download/23.2.0/appwrite-cli-win-arm64.exe"
+$GITHUB_x64_URL = "https://github.com/appwrite/sdk-for-cli/releases/download/24.0.0/appwrite-cli-win-x64.exe"
+$GITHUB_arm64_URL = "https://github.com/appwrite/sdk-for-cli/releases/download/24.0.0/appwrite-cli-win-arm64.exe"
 
 $APPWRITE_BINARY_NAME = "appwrite.exe"
 

install.ps1

@@ -120,7 +120,7 @@ verifyMacOSCodeSignature() {
 downloadBinary() {
     echo "[2/5] Downloading executable for $OS ($ARCH) ..."
 
-    GITHUB_LATEST_VERSION="23.2.0"
+    GITHUB_LATEST_VERSION="24.0.0"
     GITHUB_FILE="appwrite-cli-${OS}-${ARCH}"
     GITHUB_URL="https://github.com/$GITHUB_REPOSITORY_NAME/releases/download/$GITHUB_LATEST_VERSION/$GITHUB_FILE"
 

install.sh

@@ -13,7 +13,6 @@ import {
   isRegionalCloudEndpoint,
   openBrowser,
 } from "../utils.js";
-import { isFlagEnabled } from "../flags.js";
 import ID from "../id.js";
 import {
   questionsListFactors,
@@ -476,8 +475,13 @@ export const loginCommand = async ({
   const configEndpoint = normalizeCloudConsoleEndpoint(
     (endpoint ?? globalConfig.getEndpoint()) || DEFAULT_ENDPOINT,
   );
-  const shouldUseCloudLogin =
-    isFlagEnabled("oauthLogin") && isCloudLoginEndpoint(configEndpoint);
+  const shouldUseCloudLogin = isCloudLoginEndpoint(configEndpoint);
+
+  if (shouldUseCloudLogin && (email || password || mfa || code)) {
+    throw new Error(
+      `Cloud sign-in happens in your browser. Run '${EXECUTABLE_NAME} login' without --email, --password, --mfa or --code — those options are for self-hosted instances.`,
+    );
+  }
 
   let oldCurrent = globalConfig.getCurrentSession();
 
@@ -493,7 +497,7 @@ export const loginCommand = async ({
 
     if (account) {
       if (
-        isFlagEnabled("oauthLogin") &&
+        shouldUseCloudLogin &&
         !globalConfig.getAccessToken() &&
         globalConfig.getCookie()
       ) {

lib/auth/login.ts

@@ -81,13 +81,13 @@ export const register = new Command("register")
 
 export const login = new Command("login")
   .description(commandDescriptions["login"])
-  .option(`--email [email]`, `Email`)
-  .option(`--password [password]`, `Password`)
+  .option(`--email [email]`, `Email, for self hosted instances`)
+  .option(`--password [password]`, `Password, for self hosted instances`)
   .option(
     `--mfa [factor]`,
-    `Factor used for MFA. Must be one of: email, phone, totp, recoveryCode`,
+    `Factor used for MFA on self hosted instances. Must be one of: email, phone, totp, recoveryCode`,
   )
-  .option(`--code [code]`, `Code used for MFA`)
+  .option(`--code [code]`, `Code used for MFA on self hosted instances`)
   .option(
     `--endpoint [endpoint]`,
     `Appwrite endpoint for self hosted instances`,

lib/commands/generic.ts

@@ -181,17 +181,17 @@ const backupsCreateRestorationCommand = backups
   .command(`create-restoration`)
   .description(`Create and trigger a new restoration for a backup on a project.
 
-For a backup of one database, the restoration resolves its destination before it is queued. Pass \`newResourceId\` to restore into that database ID, including the archived database ID to overwrite it. When \`newResourceId\` is omitted, a new database ID is generated and returned in \`options\`.
+For a backup of one database, the restoration resolves its destination before it is queued. When \`newResourceId\` is omitted, the archived database is restored in place and its own ID is returned in \`options\`. Pass a different \`newResourceId\` to restore alongside it as a new database instead.
 
 The restoration migration records the archived database in \`resourceId\` and \`resourceType\`, and the resolved database in \`destinationResourceId\` and \`destinationResourceType\`. Database types are stored canonically as \`database\`, \`documentsdb\`, or \`vectorsdb\`. Project-wide restorations leave these fields empty because they do not have a single source or destination database.
 
 To list every migration related to one database, use its canonical type in a nested \`OR(AND(...), AND(...), AND(...))\` across the root, parent, and destination relation pairs: \`(resourceType, resourceId)\`, \`(parentResourceType, parentResourceId)\`, and \`(destinationResourceType, destinationResourceId)\`. Legacy and TablesDB databases use \`database\`; the operational \`resourceType\` of a table migration is not rewritten to \`tablesdb\`.
 
-When restoring a DocumentsDB or VectorsDB database to a new resource from a dedicated source, the restore provisions a fresh dedicated backing database at the source database's own specification.
+When restoring a DocumentsDB or VectorsDB database from a dedicated source, the restore provisions a fresh dedicated backing database at the source database's own specification and lands the data there. An in-place restore swaps the database onto that backing only once the restore has succeeded, and retires the backing it displaced only once that swap is confirmed, so the source keeps serving its own data until the restored data is in place and any failure leaves it untouched. A serverless source has no dedicated backing to clone and restores onto the archived database instead.
 `)
   .requiredOption(`--archive-id <archive-id>`, `Backup archive ID to restore`)
   .requiredOption(`--services [services...]`, `Array of services to restore`)
-  .option(`--new-resource-id <new-resource-id>`, `Destination resource ID. Omit to generate a new ID, or pass the archived resource ID to overwrite it. Valid chars are a-z, A-Z, 0-9, period, hyphen, and underscore. Can't start with a special char. Max length is 36 chars.`)
+  .option(`--new-resource-id <new-resource-id>`, `Destination resource ID. Omit to restore the archived resource in place, or pass a different ID to restore alongside it as a new resource. Valid chars are a-z, A-Z, 0-9, period, hyphen, and underscore. Can't start with a special char. Max length is 36 chars.`)
   .option(`--new-resource-name <new-resource-name>`, `Database name. Max length: 128 chars.`)
   .action(
     actionRunner(

lib/commands/services/backups.ts

@@ -221,10 +221,11 @@ If you're creating a new file using one of the Appwrite SDKs, all the chunking l
   .requiredOption(`--file-id <file-id>`, `File ID. Choose a custom ID or generate a random ID with \`ID.unique()\`. Valid chars are a-z, A-Z, 0-9, period, hyphen, and underscore. Can't start with a special char. Max length is 36 chars.`)
   .requiredOption(`--file <file>`, `Binary file. Appwrite SDKs provide helpers to handle file input. Learn about file input (https://appwrite.io/docs/products/storage/upload-download#input-file).`)
   .option(`--permissions [permissions...]`, `An array of permission strings. By default, only the current user is granted all permissions. Learn more about permissions (https://appwrite.io/docs/permissions).`)
+  .option(`--folder <folder>`, `Virtual folder to place the file in, for example "photos/2026". Nest folders with \`/\`. Defaults to the bucket root.`)
   .action(
     actionRunner(
-      async ({ bucketId, fileId, file, permissions }) =>
-        parse(await (await getStorageClient()).createFile(bucketId, fileId, file !== undefined ? await resolveFileParam(file) : undefined, permissions)),
+      async ({ bucketId, fileId, file, permissions, folder }) =>
+        parse(await (await getStorageClient()).createFile(bucketId, fileId, file !== undefined ? await resolveFileParam(file) : undefined, permissions, folder)),
     ),
   );