docs: Use sentry-cli deploys instead of legacy command (#10287)

Replace all mentions of the legacy `sentry-cli releases deploys ...` commands with the `sentry-cli deploys ...` commands introduced in Sentry CLI v2.0.0. Resolves #10268
getsentry · Jun 6, 2024 · b665c2d · b665c2d
1 parent f778392
commit b665c2d
Show file tree

Hide file tree

Showing 4 changed files with 7 additions and 7 deletions.
diff --git a/docs/cli/releases.mdx b/docs/cli/releases.mdx
@@ -236,7 +236,7 @@ sentry-cli files delete --release "$VERSION" --all
 You can also associate deploys with releases. To create a deploy you first create a release and then a deploy for it. At the very least, you should supply the “environment” the deploy goes to (production, staging etc.). You can freely define this:
 
 ```bash
-sentry-cli releases deploys "$VERSION" new -e ENVIRONMENT
+sentry-cli deploys new --release "$VERSION" -e ENVIRONMENT
 ```
 
 Optionally, you can also define how long the deploy took:
@@ -245,11 +245,11 @@ Optionally, you can also define how long the deploy took:
 start=$(date +%s)
 ...
 now=$(date +%s)
-sentry-cli releases deploys "$VERSION" new -e ENVIRONMENT -t $((now-start))
+sentry-cli deploys new --release "$VERSION" -e ENVIRONMENT -t $((now-start))
 ```
 
 Deploys can be listed too (however they cannot be deleted):
 
 ```bash
-sentry-cli releases deploys "$VERSION" list
+sentry-cli deploys list --release "$VERSION"
 ```
diff --git a/docs/product/releases/setup/release-automation/circleci/index.mdx b/docs/product/releases/setup/release-automation/circleci/index.mdx
@@ -61,7 +61,7 @@ notify-sentry-deploy:
           sentry-cli releases set-commits $SENTRY_RELEASE --auto
           sentry-cli releases files $SENTRY_RELEASE upload-sourcemaps path-to-sourcemaps-if-applicable
           sentry-cli releases finalize $SENTRY_RELEASE
-          sentry-cli releases deploys $SENTRY_RELEASE new -e $SENTRY_ENVIRONMENT
+          sentry-cli deploys new -e $SENTRY_ENVIRONMENT
 ```
 
 For more details about the release management concepts in the snippet above, see the full documentation on [release management](/product/cli/releases/).

diff --git a/docs/product/releases/setup/release-automation/jenkins/index.mdx b/docs/product/releases/setup/release-automation/jenkins/index.mdx
@@ -69,7 +69,7 @@ pipeline {
                     sentry-cli releases set-commits $SENTRY_RELEASE --auto
                     sentry-cli releases files $SENTRY_RELEASE upload-sourcemaps /path/to/sourcemaps
                     sentry-cli releases finalize $SENTRY_RELEASE
-                    sentry-cli releases deploys $SENTRY_RELEASE new -e $SENTRY_ENVIRONMENT
+                    sentry-cli deploys new -e $SENTRY_ENVIRONMENT
                 '''
             }
         }
@@ -108,7 +108,7 @@ If you're using Freestyle projects, you need to add another build step after dep
    sentry-cli releases set-commits $SENTRY_RELEASE --auto
    sentry-cli releases files $SENTRY_RELEASE upload-sourcemaps path-to-sourcemaps-if-applicable
    sentry-cli releases finalize $SENTRY_RELEASE
-   sentry-cli releases deploys $SENTRY_RELEASE new -e $SENTRY_ENVIRONMENT
+   sentry-cli deploys new -e $SENTRY_ENVIRONMENT
    ```
 
    **Notes**:

diff --git a/docs/product/releases/setup/release-automation/travis-ci/index.mdx b/docs/product/releases/setup/release-automation/travis-ci/index.mdx
@@ -54,7 +54,7 @@ jobs:
         sentry-cli releases set-commits $SENTRY_RELEASE --auto
         sentry-cli releases files $SENTRY_RELEASE upload-sourcemaps path-to-sourcemaps-if-applicable
         sentry-cli releases finalize $SENTRY_RELEASE
-        sentry-cli releases deploys $SENTRY_RELEASE new -e $SENTRY_ENVIRONMENT
+        sentry-cli deploys new -e $SENTRY_ENVIRONMENT
 ```
 
 For more details about the release management concepts in the snippet above, see the full documentation on [release management](/product/cli/releases/).