diff --git a/packages/contentstack/README.md b/packages/contentstack/README.md
index 2e12d2bdc8..215e1e0cba 100644
--- a/packages/contentstack/README.md
+++ b/packages/contentstack/README.md
@@ -41,12 +41,9 @@ USAGE
 * [`csdx cm:branches:delete [-uid <value>] [-k <value>]`](#csdx-cmbranchesdelete--uid-value--k-value)
 * [`csdx cm:branches:diff [--base-branch <value>] [--compare-branch <value>] [-k <value>][--module <value>] [--format <value>] [--csv-path <value>]`](#csdx-cmbranchesdiff---base-branch-value---compare-branch-value--k-value--module-value---format-value---csv-path-value)
 * [`csdx cm:branches:merge [-k <value>][--compare-branch <value>] [--no-revert] [--export-summary-path <value>] [--use-merge-summary <value>] [--comment <value>] [--base-branch <value>]`](#csdx-cmbranchesmerge--k-value--compare-branch-value---no-revert---export-summary-path-value---use-merge-summary-value---comment-value---base-branch-value)
-<<<<<<< HEAD
-=======
 * [`csdx cm:branches:merge-status -k <value> --merge-uid <value>`](#csdx-cmbranchesmerge-status--k-value---merge-uid-value)
-* [`csdx cm:bulk-publish`](#csdx-cmbulk-publish)
-* [`csdx cm:stacks:audit`](#csdx-cmstacksaudit)
-* [`csdx cm:stacks:audit:fix`](#csdx-cmstacksauditfix)
+* [`csdx cm:stacks:migration [-k <value>] [-a <value>] [--file-path <value>] [--branch <value>] [--config-file <value>] [--config <value>] [--multiple]`](#csdx-cmstacksmigration--k-value--a-value---file-path-value---branch-value---config-file-value---config-value---multiple)
+* [`csdx cm:stacks:clone [--source-branch <value>] [--target-branch <value>] [--source-management-token-alias <value>] [--destination-management-token-alias <value>] [-n <value>] [--type a|b] [--source-stack-api-key <value>] [--destination-stack-api-key <value>] [--import-webhook-status disable|current]`](#csdx-cmstacksclone---source-branch-value---target-branch-value---source-management-token-alias-value---destination-management-token-alias-value--n-value---type-ab---source-stack-api-key-value---destination-stack-api-key-value---import-webhook-status-disablecurrent)
 * [`csdx cm:stacks:bulk-assets`](#csdx-cmstacksbulk-assets)
 * [`csdx cm:stacks:bulk-entries`](#csdx-cmstacksbulk-entries)
 * [`csdx cm:stacks:clone [--source-branch <value>] [--target-branch <value>] [--source-management-token-alias <value>] [--destination-management-token-alias <value>] [-n <value>] [--type a|b] [--source-stack-api-key <value>] [--destination-stack-api-key <value>] [--import-webhook-status disable|current]`](#csdx-cmstacksclone---source-branch-value---target-branch-value---source-management-token-alias-value---destination-management-token-alias-value--n-value---type-ab---source-stack-api-key-value---destination-stack-api-key-value---import-webhook-status-disablecurrent)
@@ -54,12 +51,7 @@ USAGE
 * [`csdx cm:stacks:import [--config <value>] [--stack-api-key <value>] [--data-dir <value>] [--alias <value>] [--module <value>] [--backup-dir <value>] [--branch <value>] [--import-webhook-status disable|current]`](#csdx-cmstacksimport---config-value---stack-api-key-value---data-dir-value---alias-value---module-value---backup-dir-value---branch-value---import-webhook-status-disablecurrent)
 * [`csdx cm:stacks:import-setup [-k <value>] [-d <value>] [-a <value>] [--modules <value,value>]`](#csdx-cmstacksimport-setup--k-value--d-value--a-value---modules-valuevalue)
 * [`csdx cm:stacks:migration [-k <value>] [-a <value>] [--file-path <value>] [--branch <value>] [--config-file <value>] [--config <value>] [--multiple]`](#csdx-cmstacksmigration--k-value--a-value---file-path-value---branch-value---config-file-value---config-value---multiple)
-* [`csdx cm:stacks:publish`](#csdx-cmstackspublish)
-* [`csdx cm:stacks:publish-clear-logs`](#csdx-cmstackspublish-clear-logs)
-* [`csdx cm:stacks:publish-configure`](#csdx-cmstackspublish-configure)
-* [`csdx cm:stacks:publish-revert`](#csdx-cmstackspublish-revert)
-* [`csdx cm:stacks:seed [--repo <value>] [--org <value>] [-k <value>] [-n <value>] [-y <value>] [-s <value>] [--locale <value>]`](#csdx-cmstacksseed---repo-value---org-value--k-value--n-value--y-value--s-value---locale-value)
-* [`csdx csdx cm:stacks:unpublish [-a <value>] [-e <value>] [-c <value>] [-y] [--locale <value>] [--branch <value>] [--retry-failed <value>] [--bulk-unpublish <value>] [--content-type <value>] [--delivery-token <value>] [--only-assets] [--only-entries]`](#csdx-csdx-cmstacksunpublish--a-value--e-value--c-value--y---locale-value---branch-value---retry-failed-value---bulk-unpublish-value---content-type-value---delivery-token-value---only-assets---only-entries)
+* [`csdx cm:stacks:seed [--repo <value>] [--org <value>] [--stack-api-key <value>] [--stack-name <value>] [-y] [--alias <value>] [--locale <value>]`](#csdx-cmstacksseed---repo-value---org-value---stack-api-key-value---stack-name-value--y---alias-value---locale-value)
 * [`csdx config:get:base-branch`](#csdx-configgetbase-branch)
 * [`csdx config:get:ea-header`](#csdx-configgetea-header)
 * [`csdx config:get:early-access-header`](#csdx-configgetearly-access-header)
@@ -367,1697 +359,159 @@ DESCRIPTION
 EXAMPLES
   $ csdx cm:branches:create
 
-  $ csdx cm:branches:create --source main -uid new_branch -k bltxxxxxxxx
-
-  $ csdx cm:branches:create --source main --uid new_branch --stack-api-key bltxxxxxxxx
-```
-
-_See code: [@contentstack/cli-cm-branches](https://github.com/contentstack/cli/blob/main/packages/contentstack-export/src/commands/cm/branches/create.ts)_
-
-## `csdx cm:branches:delete [-uid <value>] [-k <value>]`
-
-Delete a branch
-
-```
-USAGE
-  $ csdx cm:branches:delete [-uid <value>] [-k <value>]
-  $ csdx cm:branches:delete [--uid <value>] [--stack-api-key <value>]
-
-FLAGS
-  -k, --stack-api-key=<value>  Stack API key
-  -y, --yes                    Force the deletion of the branch by skipping the confirmation
-      --uid=<value>            Branch UID to be deleted
-
-DESCRIPTION
-  Delete a branch
-
-EXAMPLES
-  $ csdx cm:branches:delete
-
-  $ csdx cm:branches:delete --uid main -k bltxxxxxxxx
-
-  $ csdx cm:branches:delete --uid main --stack-api-key bltxxxxxxxx
-
-  $ csdx cm:branches:delete --uid main --stack-api-key bltxxxxxxxx --yes
-```
-
-_See code: [@contentstack/cli-cm-branches](https://github.com/contentstack/cli/blob/main/packages/contentstack-export/src/commands/cm/branches/delete.ts)_
-
-## `csdx cm:branches:diff [--base-branch <value>] [--compare-branch <value>] [-k <value>][--module <value>] [--format <value>] [--csv-path <value>]`
-
-Differences between two branches
-
-```
-USAGE
-  $ csdx cm:branches:diff [--base-branch <value>] [--compare-branch <value>] [-k <value>][--module <value>] [--format
-    <value>] [--csv-path <value>]
-
-FLAGS
-  -k, --stack-api-key=<value>   [optional] Provide the stack API key to show the difference between branches.
-      --base-branch=<value>     [optional] Base branch (Target branch).
-      --compare-branch=<value>  [optional] Compare branch (Source branch).
-      --csv-path=<value>        [optional] Custom path for CSV output file. If not provided, will use the current
-                                working directory.
-      --format=<option>         [default: compact-text] [default: compact-text] [optional] Type of flags to show the
-                                difference between two branches. <options: compact-text, detailed-text>
-                                <options: compact-text|detailed-text>
-      --module=<option>         [optional] Module. <options: content-types, global-fields, all>
-                                <options: content-types|global-fields|all>
-
-DESCRIPTION
-  Differences between two branches
-
-EXAMPLES
-  $ csdx cm:branches:diff
-
-  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx"
-
-  $ csdx cm:branches:diff --compare-branch "develop"
-
-  $ csdx cm:branches:diff --compare-branch "develop" --stack-api-key "bltxxxxxxxx"
-
-  $ csdx cm:branches:diff --compare-branch "develop" --module "content-types"
-
-  $ csdx cm:branches:diff --module "content-types" --format "detailed-text"
-
-  $ csdx cm:branches:diff --compare-branch "develop" --format "detailed-text"
-
-  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main"
-
-  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main" --compare-branch "develop"
-
-  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main" --module "content-types"
-
-  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main" --compare-branch "develop" --module "content-types"
-
-  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main" --compare-branch "develop" --module "content-types" --format "detailed-text"
-
-  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main" --compare-branch "develop" --module "content-types" --format "compact-text"
-
-  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main" --compare-branch "develop" --module "content-types" --format "detailed-text" --csv-path "./reports/diff-report.csv"
-```
-
-_See code: [@contentstack/cli-cm-branches](https://github.com/contentstack/cli/blob/main/packages/contentstack-export/src/commands/cm/branches/diff.ts)_
-
-## `csdx cm:branches:merge [-k <value>][--compare-branch <value>] [--no-revert] [--export-summary-path <value>] [--use-merge-summary <value>] [--comment <value>] [--base-branch <value>]`
-
-Merge changes from a branch
-
-```
-USAGE
-  $ csdx cm:branches:merge [-k <value>][--compare-branch <value>] [--no-revert] [--export-summary-path <value>]
-    [--use-merge-summary <value>] [--comment <value>] [--base-branch <value>]
-
-FLAGS
-  -k, --stack-api-key=<value>        [optional] Provide stack API key to show the difference between the branches.
-      --base-branch=<value>          [optional] Base branch (Target branch).
-      --comment=<value>              [optional] Pass a comment.
-      --compare-branch=<value>       [optional] Compare branch (Source branch).
-      --export-summary-path=<value>  [optional] Export summary file path.
-      --no-revert                    [optional] If passed, will not create the new revert branch.
-      --use-merge-summary=<value>    [optional] Path of merge summary file.
-
-DESCRIPTION
-  Merge changes from a branch
-
-EXAMPLES
-  $ csdx cm:branches:merge --stack-api-key bltxxxxxxxx --compare-branch feature-branch
-
-  $ csdx cm:branches:merge --stack-api-key bltxxxxxxxx --comment "merge comment"
-
-  $ csdx cm:branches:merge -k bltxxxxxxxx --base-branch base-branch
-
-  $ csdx cm:branches:merge --export-summary-path file/path
-
-  $ csdx cm:branches:merge --use-merge-summary file-path
-
-  $ csdx cm:branches:merge -k bltxxxxxxxx --no-revert
-
-  $ csdx cm:branches:merge -k bltxxxxxxxx --compare-branch feature-branch --no-revert
-```
-
-_See code: [@contentstack/cli-cm-branches](https://github.com/contentstack/cli/blob/main/packages/contentstack-export/src/commands/cm/branches/merge.ts)_
-
-<<<<<<< HEAD
-=======
-## `csdx cm:branches:merge-status -k <value> --merge-uid <value>`
-
-Check the status of a branch merge job
-
-```
-USAGE
-  $ csdx cm:branches:merge-status -k <value> --merge-uid <value>
-
-FLAGS
-  -k, --stack-api-key=<value>  (required) Provide your stack API key.
-      --merge-uid=<value>      (required) Merge job UID to check status for.
-
-DESCRIPTION
-  Check the status of a branch merge job
-
-EXAMPLES
-  $ csdx cm:branches:merge-status -k bltxxxxxxxx --merge-uid merge_abc123
-
-  $ csdx cm:branches:merge-status --stack-api-key bltxxxxxxxx --merge-uid merge_abc123
-```
-
-_See code: [@contentstack/cli-cm-branches](https://github.com/contentstack/cli/blob/main/packages/contentstack-export/src/commands/cm/branches/merge-status.ts)_
-
-## `csdx cm:bulk-publish`
-
-Bulk Publish script for managing entries and assets
-
-```
-USAGE
-  $ csdx cm:bulk-publish
-
-DESCRIPTION
-  Bulk Publish script for managing entries and assets
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/bulk-publish/index.js)_
-
-## `csdx cm:entries:update-and-publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--content-types <value>] [-t <value>] [-e <value>] [-c <value>] [-y] [--locales <value>] [--branch <value>]`
-
-Add fields from updated content types to their respective entries
-
-```
-USAGE
-  $ csdx cm:bulk-publish:add-fields cm:entries:update-and-publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>]
-    [--content-types <value>] [-t <value>] [-e <value>] [-c <value>] [-y] [--locales <value>] [--branch <value>]
-
-FLAGS
-  -B, --branch=<value>            [default: main] The name of the branch where you want to perform the bulk publish
-                                  operation. If you don’t mention the branch name, then by default the content from the
-                                  main branch will be published.
-  -a, --alias=<value>             Alias (name) of the management token. You must use either the --alias flag or the
-                                  --stack-api-key flag.
-  -c, --config=<value>            (optional) The path of the optional configuration JSON file containing all the options
-                                  for a single run. Refer to the configure command to create a configuration file.
-  -e, --environments=<value>...   The name of the environment on which entries will be published. In case of multiple
-                                  environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>     API key of the source stack. You must use either the --stack-api-key flag or the
-                                  --alias flag.
-  -l, --locales=<value>...        Locales in which entries will be published, e.g., en-us. In the case of multiple
-                                  locales, specify the codes separated by spaces.
-  -t, --contentTypes=<value>...   The Contenttypes from which entries will be published.
-  -y, --yes                       Set it to true to process the command with the current configuration.
-      --api-version=<value>       API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-publish=<value>      [default: true] Set this flag to use Contentstack’s Bulk Publish APIs. It is true, by
-                                  default.
-      --content-types=<value>...  The UID of the content type ID whose entries you want to publish in bulk. In case of
-                                  multiple content types, specify their IDs separated by spaces.
-      --force                     Update and publish all entries even if no fields have been added.
-      --retry-failed=<value>      Use this option to retry publishing the failed entries from the logfile. Specify the
-                                  name of the logfile that lists failed publish calls. If this option is used, it will
-                                  override all other flags.
-
-DESCRIPTION
-  Add fields from updated content types to their respective entries
-  The update-and-publish command is used to update existing entries with the updated schema of the respective content
-  type
-
-  Note: Content types, Environments and Locales are required to execute the command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-
-ALIASES
-  $ csdx cm:bulk-publish:add-fields
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:update-and-publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:stacks:publish-configure -a [ALIAS]`
-
-  $ csdx cm:entries:update-and-publish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:update-and-publish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed
-
-  $ csdx cm:entries:update-and-publish --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch
-
-  $ csdx cm:entries:update-and-publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key
-
-  $ csdx cm:entries:update-and-publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] --stack-api-key [STACK API KEY]
-```
-
-## `csdx cm:assets:publish [-a <value>] [--retry-failed <value>] [-e <value>] [--folder-uid <value>] [--bulk-publish <value>] [-c <value>] [-y] [--locales <value>] [--branch <value>] [--delivery-token <value>] [--source-env <value>]`
-
-Publish assets to the specified environments
-
-```
-USAGE
-  $ csdx cm:bulk-publish:assets cm:assets:publish [-a <value>] [--retry-failed <value>] [-e <value>] [--folder-uid <value>]
-    [--bulk-publish <value>] [-c <value>] [-y] [--locales <value>] [--branch <value>] [--delivery-token <value>]
-    [--source-env <value>]
-
-FLAGS
-  -B, --branch=<value>           [default: main] The name of the branch where you want to perform the bulk publish
-                                 operation. If you don’t mention the branch name, then by default the assets from the
-                                 main branch will be published.
-  -a, --alias=<value>            Alias (name) for the management token. You must use either the --alias flag or the
-                                 --stack-api-key flag.
-  -c, --config=<value>           (optional) The path of the optional configuration JSON file containing all the options
-                                 for a single run. Refer to the configure command to create a configuration file.
-  -e, --environments=<value>...  The name of the environment on which entries will be published. In case of multiple
-                                 environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>    API key of the source stack. You must use either the --stack-api-key flag or the
-                                 --alias flag.
-  -l, --locales=<value>...       Locales in which assets will be published, e.g., en-us. In the case of multiple
-                                 locales, specify the codes separated by spaces.
-  -y, --yes                      Set it to true to process the command with the current configuration.
-      --api-version=<value>      API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-publish=<value>     [default: true] Set this flag to use Contentstack’s Bulk Publish APIs. It is true, by
-                                 default.
-      --delivery-token=<value>   The delivery token of the source environment.
-      --folder-uid=<value>       (optional) The UID of the Assets’ folder from which the assets need to be published.
-                                 The default value is cs_root.
-      --retry-failed=<value>     Use this option to retry publishing the failed assets from the logfile. Specify the
-                                 name of the logfile that lists failed publish calls. If this option is used, it will
-                                 override all other flags.
-      --source-env=<value>       Source environment
-
-DESCRIPTION
-  Publish assets to the specified environments
-  The assets command is used to publish assets from the specified stack, to the specified environments
-
-  Note: Environment(s) and Locale(s) are required to execute the command successfully
-  But, if retryFailed flag is set, then only a logfile is required
-
-
-ALIASES
-  $ csdx cm:bulk-publish:assets
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:assets:publish --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE] --alias [MANAGEMENT TOKEN ALIAS]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:stacks:publish-configure -a [ALIAS]`
-
-  $ csdx cm:assets:publish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:assets:publish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed flag
-
-  $ csdx cm:assets:publish --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch flag
-
-  $ csdx cm:assets:publish --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME]
-
-
-
-  Using --source-env
-
-  $ csdx cm:assets:publish --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] --source-env [SOURCE ENVIRONMENT] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --stack-api-key flag
-
-  $ csdx cm:assets:publish --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE] --stack-api-key [STACK API KEY]
-```
-
-## `csdx cm:bulk-publish:clear`
-
-Clear the log folder
-
-```
-USAGE
-  $ csdx cm:bulk-publish:clear [--log-files-count] [-y]
-
-FLAGS
-  -y, --yes              Delete all files without asking for confirmation
-      --log-files-count  List number of log files
-
-DESCRIPTION
-  Clear the log folder
-
-ALIASES
-  $ csdx cm:bulk-publish:clear
-
-EXAMPLES
-  $ csdx cm:stacks:publish-clear-logs
-
-  $ csdx cm:stacks:publish-clear-logs --log-files-count
-
-  $ csdx cm:stacks:publish-clear-logs --yes
-
-  $ csdx cm:stacks:publish-clear-logs -y
-```
-
-## `csdx cm:bulk-publish:configure`
-
-The configure command is used to generate a configuration file for publish scripts.
-
-```
-USAGE
-  $ csdx cm:bulk-publish:configure [-a <value>] [-k <value>]
-
-FLAGS
-  -a, --alias=<value>          Name (alias) of the management token you want to use. You must use either the --alias
-                               flag or the --stack-api-key flag.
-  -k, --stack-api-key=<value>  API key of the source stack. You must use either the --stack-api-key flag or the --alias
-                               flag.
-
-DESCRIPTION
-  The configure command is used to generate a configuration file for publish scripts.
-
-ALIASES
-  $ csdx cm:bulk-publish:configure
-
-EXAMPLES
-  $ csdx cm:stacks:publish-configure
-
-  $ csdx cm:stacks:publish-configure -a <management_token_alias>
-
-  $ csdx cm:stacks:publish-configure --alias <management_token_alias>
-
-  $ csdx cm:stacks:publish-configure --stack-api-key <stack_api_key>
-```
-
-## `csdx cm:bulk-publish:cross-publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--content-type <value>] [--locales <value>] [--source-env <value>] [--environments <value>] [--delivery-token <value>] [-c <value>] [-y] [--branch <value>] [--onlyAssets] [--onlyEntries] [--include-variants]`
-
-Publish entries and assets from one environment to other environments
-
-```
-USAGE
-  $ csdx cm:bulk-publish:cross-publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--content-type <value>]
-    [--locales <value>] [--source-env <value>] [--environments <value>] [--delivery-token <value>] [-c <value>] [-y]
-    [--branch <value>] [--onlyAssets] [--onlyEntries] [--include-variants]
-
-FLAGS
-  -B, --branch=<value>           [default: main] Specify the branch to fetch the content (by default the main branch is
-                                 selected)
-  -a, --alias=<value>            Alias(name) for the management token
-  -c, --config=<value>           Path to the config file
-  -k, --stack-api-key=<value>    Stack API key to be used
-  -y, --yes                      Agree to process the command with the current configuration
-      --api-version=<value>      API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-publish=<value>     [default: true] Set this flag to use Contentstack’s Bulk Publish APIs. It is true, by
-                                 default.
-      --content-type=<value>...  The Contenttypes from which entries will be published
-      --delivery-token=<value>   The delivery token of the source environment.
-      --environments=<value>...  Destination Environments
-      --include-variants         Include Variants flag will publish all associated variant entries.
-      --locales=<value>          Source locale
-      --onlyAssets               Unpublish only assets
-      --onlyEntries              Unpublish only entries
-      --retry-failed=<value>     (optional) Retry publishing failed entries from the logfile (this flag overrides all
-                                 other flags)
-      --source-env=<value>       Source Env
-
-DESCRIPTION
-  Publish entries and assets from one environment to other environments
-  The cross-publish command is used to publish entries and assets from one environment to other environments
-
-  Note: Content Type, Environment, Destination Environment(s) and Locale are required to execute the command
-  successfully
-  But, if retryFailed flag is set, then only a logfile is required
-
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:bulk-publish:cross-publish --content-type [CONTENT TYPE] --source-env [SOURCE ENV] --environments [DESTINATION ENVIRONMENT] --locales [LOCALE] -a [MANAGEMENT TOKEN ALIAS] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:bulk-publish:configure -a [ALIAS]`
-
-  $ csdx cm:bulk-publish:cross-publish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:bulk-publish:cross-publish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed flag
-
-  $ csdx cm:bulk-publish:cross-publish --retry-failed [LOG FILE NAME]
-
-  $ csdx cm:bulk-publish:cross-publish -r [LOG FILE NAME]
-
-
-
-  Using --branch flag
-
-  $ csdx cm:bulk-publish:cross-publish --content-type [CONTENT TYPE] --source-env [SOURCE ENV] --environments [DESTINATION ENVIRONMENT] --locales [LOCALE] -a [MANAGEMENT TOKEN ALIAS] --delivery-token [DELIVERY TOKEN] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key flag
-
-  $ csdx cm:bulk-publish:cross-publish --content-type [CONTENT TYPE] --source-env [SOURCE ENV] --environments [DESTINATION ENVIRONMENT] --locales [LOCALE] --stack-api-key [STACK API KEY] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --include-variants flag
-
-  $ csdx cm:bulk-publish:cross-publish --content-type [CONTENT TYPE] --source-env [SOURCE ENV] --environments [DESTINATION ENVIRONMENT] --locales [LOCALE] --stack-api-key [STACK API KEY] --delivery-token [DELIVERY TOKEN] [--include-variants]
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/bulk-publish/cross-publish.js)_
-
-## `csdx cm:entries:publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--publish-all-content-types] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>] [--delivery-token <value>] [--source-env <value>] [--entry-uid <value>] [--include-variants]`
-
-Publish entries from multiple contenttypes to multiple environments and locales
-
-```
-USAGE
-  $ csdx cm:bulk-publish:entries cm:entries:publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>]
-    [--publish-all-content-types] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch
-    <value>] [--delivery-token <value>] [--source-env <value>] [--entry-uid <value>] [--include-variants]
-
-FLAGS
-  -B, --branch=<value>             [default: main] The name of the branch where you want to perform the bulk publish
-                                   operation. If you don’t mention the branch name, then by default the content from
-                                   main branch will be published.
-  -a, --alias=<value>              Alias (name) of the management token. You must use either the --alias flag or the
-                                   --stack-api-key flag.
-  -c, --config=<value>             (optional) The path of the optional configuration JSON file containing all the
-                                   options for a single run. Refer to the configure command to create a configuration
-                                   file.
-  -e, --environments=<value>...    The name of the environment on which entries will be published. In case of multiple
-                                   environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>      API key of the source stack. You must use either the --stack-api-key flag or the
-                                   --alias flag.
-  -l, --locales=<value>...         Locales in which entries will be published, e.g., en-us. In the case of multiple
-                                   locales, specify the codes separated by spaces.
-  -y, --yes                        Set it to true to process the command with the current configuration.
-      --api-version=<value>        API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-publish=<value>       [default: true] Set this flag to use Contentstack's Bulk Publish APIs. This flag is
-                                   set to true, by default.
-      --content-types=<value>...   The UID of the content type(s) whose entries you want to publish in bulk. In case of
-                                   multiple content types, specify the IDs separated by spaces.
-      --delivery-token=<value>     The delivery token of the source environment.
-      --entry-uid=<value>          Entry Uid for publish all associated variant entries.
-      --include-variants           Include Variants flag will publish all associated variant entries with base entry.
-      --publish-all-content-types  (optional) Set it to true to bulk publish entries from all content types. If the
-                                   --content-types option is already used, then you cannot use this option.
-      --retry-failed=<value>       (optional) Use this option to retry publishing the failed entries/ assets from the
-                                   logfile. Specify the name of the logfile that lists failed publish calls. If this
-                                   option is used, it will override all other flags.
-      --source-env=<value>         Source environment
-
-DESCRIPTION
-  Publish entries from multiple contenttypes to multiple environments and locales
-  The publish command is used to publish entries from the specified content types, to the
-  specified environments and locales
-
-  Note: Content Types, Environments and Locales are required to execute the command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-
-ALIASES
-  $ csdx cm:bulk-publish:entries
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:stacks:publish-configure -a [ALIAS]`
-
-  $ csdx cm:entries:publish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:publish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed
-
-  $ csdx cm:entries:publish --retry-failed [LOG FILE NAME]
-
-  $ csdx cm:entries:publish -r [LOG FILE NAME]
-
-
-
-  Using --branch
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME]
-
-
-
-  Using --source-env
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS] --source-env [SOURCE ENVIRONMENT] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --stack-api-key
-
-  $ csdx cm:entries:publish -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] --stack-api-key [STACK API KEY] --source-env [SOURCE ENVIRONMENT] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --include-variants
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] --stack-api-key [STACK API KEY] --source-env [SOURCE ENVIRONMENT] --delivery-token [DELIVERY TOKEN] [--include-variants]
-
-
-
-  Using --entry-uid and --include-variants
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] --stack-api-key [STACK API KEY] --source-env [SOURCE ENVIRONMENT] --delivery-token [DELIVERY TOKEN] --entry-uid [ENTRY UID] [--include-variants]
-```
-
-## `csdx cm:entries:publish-modified [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]`
-
-Publish edited entries from a specified content type to the given locales and environments
-
-```
-USAGE
-  $ csdx cm:bulk-publish:entry-edits cm:entries:publish-modified [-a <value>] [--retry-failed <value>] [--bulk-publish <value>]
-    [--source-env <value>] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch
-    <value>]
-
-FLAGS
-  -B, --branch=<value>            [default: main] The name of the branch where you want to perform the bulk publish
-                                  operation. If you don't mention the branch name, then by default the entries from main
-                                  branch will be published.
-  -a, --alias=<value>             Alias (name) of the management token. You must use either the --alias flag or the
-                                  --stack-api-key flag.
-  -c, --config=<value>            (optional) The path of the optional configuration JSON file containing all the options
-                                  for a single run. Refer to the configure command to create a configuration file.
-  -e, --environments=<value>...   The name of the environment(s) on which the entries will be published. In case of
-                                  multiple environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>     API key of the source stack. You must use either the --stack-api-key flag or the
-                                  --alias flag.
-  -l, --locales=<value>...        Locales in which entries will be published, e.g., en-us. In the case of multiple
-                                  locales, specify the codes separated by spaces.
-  -y, --yes                       Set it to true to process the command with the current configuration.
-      --api-version=<value>       API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-publish=<value>      [default: true] Set this flag to use Contentstack's Bulk Publish APIs. It is true, by
-                                  default.
-      --content-types=<value>...  The UID of the content type(s) whose edited entries you want to publish in bulk. In
-                                  case of multiple content types, specify the IDs separated by spaces.
-      --retry-failed=<value>      (optional) Use this option to retry publishing the failed entries/assets from the
-                                  logfile. Specify the name of the logfile that lists failed publish calls. If this
-                                  option is used, it will override all other flags
-      --source-env=<value>        The name of the source environment where the entries were initially published.
-
-DESCRIPTION
-  Publish edited entries from a specified content type to the given locales and environments
-  The publish-modified command is used to publish entries from the specified content types, to the
-  specified environments and locales
-
-  Note: Content type(s), Source Environment, Destination Environment(s) and Locale(s) are required to execute the
-  command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-
-ALIASES
-  $ csdx cm:bulk-publish:entry-edits
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:publish-modified --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --source-env [SOURCE_ENV] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:stacks:publish-configure -a [ALIAS]`
-
-  $ csdx cm:entries:publish-modified --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:publish-modified -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed
-
-  $ csdx cm:entries:publish-modified --retry-failed [LOG FILE NAME]
-
-  $ csdx cm:entries:publish-modified -r [LOG FILE NAME]
-
-
-
-  Using --branch
-
-  $ csdx cm:entries:publish-modified --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --source-env [SOURCE_ENV] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key
-
-  $ csdx cm:entries:publish-modified --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --source-env [SOURCE_ENV] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -stack-api-key [STACK API KEY]
-```
-
-## `csdx cm:entries:publish-non-localized-fields [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]`
-
-Publish non-localized fields for the given content types, from a particular source environment to the specified environments
-
-```
-USAGE
-  $ csdx cm:bulk-publish:nonlocalized-field-changes cm:entries:publish-non-localized-fields [-a <value>] [--retry-failed <value>]
-    [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [-e <value>] [-c <value>] [-y] [--branch
-    <value>]
-
-FLAGS
-  -B, --branch=<value>            [default: main] The name of the branch where you want to perform the bulk publish
-                                  operation. If you don’t mention the branch name, then by default the content from the
-                                  main branch will be published.
-  -a, --alias=<value>             Alias (name) of the management token. You must use either the --alias flag or the
-                                  --stack-api-key flag.
-  -c, --config=<value>            (optional) The path of the optional configuration JSON file containing all the options
-                                  for a single run. Refer to the configure command to create a configuration file.
-  -e, --environments=<value>...   The name of the environment on which entries will be published. In case of multiple
-                                  environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>     API key of the source stack. You must use either the --stack-api-key flag or the
-                                  --alias flag.
-  -y, --yes                       Set it to true to process the command with the current configuration.
-      --api-version=<value>       API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-publish=<value>      [default: true] Set this flag to use Contentstack’s Bulk Publish APIs. It is true, by
-                                  default.
-      --content-types=<value>...  The UID of the content type whose entries you want to publish in bulk. In case of
-                                  multiple content types, specify their IDs separated by spaces.
-      --retry-failed=<value>      Use this option to retry publishing the failed entries from the logfile. Specify the
-                                  name of the logfile that lists failed publish calls. If this option is used, it will
-                                  override all other flags.
-      --source-env=<value>        The name of the source environment.
-
-DESCRIPTION
-  Publish non-localized fields for the given content types, from a particular source environment to the specified
-  environments
-  The non-localized field changes command is used to publish non-localized field changes from the given content types to
-  the specified environments
-
-  Note: Content types, Environments and Source Environment are required to execute this command successfully.
-  But, if retryFailed flag is set, then only a logfile is required
-
-ALIASES
-  $ csdx cm:bulk-publish:nonlocalized-field-changes
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:publish-non-localized-fields --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --alias [MANAGEMENT TOKEN ALIAS] --source-env [SOURCE ENV]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:bulk-publish:configure -a [ALIAS]`
-
-  $ csdx cm:entries:publish-non-localized-fields --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:publish-non-localized-fields -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed flag
-
-  $ csdx cm:entries:publish-non-localized-fields --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch flag
-
-  $ csdx cm:entries:publish-non-localized-fields --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --alias [MANAGEMENT TOKEN ALIAS] --source-env [SOURCE ENV] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key flag
-
-  $ csdx cm:entries:publish-non-localized-fields --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --stack-api-key [STACK API KEY] --source-env [SOURCE ENV]
-```
-
-## `csdx cm:bulk-publish:revert`
-
-Revert publish operations by using a log file
-
-```
-USAGE
-  $ csdx cm:bulk-publish:revert [--retry-failed <value>] [--log-file <value>]
-
-FLAGS
-  --log-file=<value>      Path of the success logfile of a particular publish action.
-  --retry-failed=<value>  (optional)  Use this option to retry publishing the failed entries from the logfile. Specify
-                          the name of the logfile that lists failed publish calls. If this option is used, it will
-                          override all other flags.
-
-DESCRIPTION
-  Revert publish operations by using a log file
-  The revert command is used to revert all publish operations performed using bulk-publish script.
-  A log file name is required to execute revert command
-
-
-ALIASES
-  $ csdx cm:bulk-publish:revert
-
-EXAMPLES
-  Using --log-file
-
-  cm:bulk-publish:revert --log-file [LOG FILE NAME]
-
-
-
-  Using --retry-failed
-
-  cm:bulk-publish:revert --retry-failed [LOG FILE NAME]
-```
-
-## `csdx csdx cm:stacks:unpublish [-a <value>] [-e <value>] [-c <value>] [-y] [--locale <value>] [--branch <value>] [--retry-failed <value>] [--bulk-unpublish <value>] [--content-type <value>] [--delivery-token <value>] [--only-assets] [--only-entries]`
-
-Unpublish entries or assets of given content types from the specified environment
-
-```
-USAGE
-  $ csdx cm:bulk-publish:unpublish csdx cm:stacks:unpublish [-a <value>] [-e <value>] [-c <value>] [-y] [--locale <value>]
-    [--branch <value>] [--retry-failed <value>] [--bulk-unpublish <value>] [--content-type <value>] [--delivery-token
-    <value>] [--only-assets] [--only-entries]
-
-FLAGS
-  -B, --branch=<value>          [default: main] Specify the branch to fetch the content from (default is main branch)
-  -a, --alias=<value>           Alias(name) for the management token
-  -c, --config=<value>          Path to the config file
-  -e, --environment=<value>     Source Environment
-  -k, --stack-api-key=<value>   Stack API key to be used
-  -l, --locale=<value>          Locale filter
-  -y, --yes                     Agree to process the command with the current configuration
-      --api-version=<value>     API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-unpublish=<value>  [default: true] This flag is set to true by default. It indicates that contentstack's
-                                bulkpublish API will be used to unpublish the entries and assets
-      --content-type=<value>    Content type filter
-      --delivery-token=<value>  The delivery token of the source environment.
-      --retry-failed=<value>    Retry publishing failed entries from the logfile (optional, overrides all other flags)
-
-DESCRIPTION
-  Unpublish entries or assets of given content types from the specified environment
-  The unpublish command is used to unpublish entries or assets from given environment
-
-  Environment (Source Environment) and Locale are required to execute the command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-  A content type can be specified for unpublishing entries, but if no content-type(s) is/are specified and --only-assets
-  is not used,
-  then all entries from all content types will be unpublished from the source environment
-
-  Note: --only-assets can be used to unpublish only assets and --only-entries can be used to unpublish only entries.
-  (--only-assets and --only-entries cannot be used together at the same time)
-
-
-ALIASES
-  $ csdx cm:bulk-publish:unpublish
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:stacks:unpublish --bulk-unpublish --content-type [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] ----delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:bulk-publish:configure --alias [ALIAS]`
-
-  $ csdx cm:stacks:unpublish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:stacks:unpublish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed flag
-
-  $ csdx cm:stacks:unpublish --retry-failed [LOG FILE NAME]
-
-
-
-  No content type
-
-  $ csdx cm:stacks:unpublish --environment [SOURCE ENV] --locale [LOCALE] (Will unpublish all entries from all content types and assets from the source environment)
-
-
-
-  Using --only-assets
-
-  $ csdx cm:stacks:unpublish --environment [SOURCE ENV] --locale [LOCALE] --only-assets (Will unpublish only assets from the source environment)
-
-
-
-  Using --only-entries
-
-  $ csdx cm:stacks:unpublish --environment [SOURCE ENV] --locale [LOCALE] --only-entries (Will unpublish only entries, all entries, from the source environment)
-
-  $ csdx cm:stacks:unpublish --contentType [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --only-entries (Will unpublish only entries, (from CONTENT TYPE) from the source environment)
-
-
-
-  Using --branch flag
-
-  $ csdx cm:stacks:unpublish --bulk-unpublish --content-type [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] --delivery-token [DELIVERY TOKEN] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key flag
-
-  $ csdx cm:stacks:unpublish --bulk-unpublish --content-type [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --stack-api-key [STACK API KEY] --delivery-token [DELIVERY TOKEN]
-```
-
-## `csdx cm:entries:publish-only-unpublished [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]`
-
-Publish unpublished entries from the source environment, to other environments and locales
-
-```
-USAGE
-  $ csdx cm:bulk-publish:unpublished-entries cm:entries:publish-only-unpublished [-a <value>] [--retry-failed <value>] [--bulk-publish
-    <value>] [--source-env <value>] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y]
-    [--branch <value>]
-
-FLAGS
-  -B, --branch=<value>            [default: main] The name of the branch where you want to perform the bulk publish
-                                  operation. If you don't mention the branch name, then by default the entries from main
-                                  branch will be published.
-  -a, --alias=<value>             Alias (name) of the management token. You must use either the --alias flag or the
-                                  --stack-api-key flag.
-  -b, --bulk-publish=<value>      [default: true] Set this flag to use Contentstack's Bulk Publish APIs. It is true, by
-                                  default.
-  -c, --config=<value>            (optional)  The path of the optional configuration JSON file containing all the
-                                  options for a single run. Refer to the configure command to create a configuration
-                                  file.
-  -e, --environments=<value>...   The name of the environment on which entries will be published. In case of multiple
-                                  environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>     API key of the source stack. You must use either the --stack-api-key flag or the
-                                  --alias flag.
-  -y, --yes                       Set it to true to process the command with the current configuration.
-      --api-version=<value>       API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2]..
-      --content-types=<value>...  The UID of the content type(s) whose entries you want to publish in bulk. In case of
-                                  multiple content types, specify their IDs separated by spaces.
-      --locales=<value>           Locale in which entries will be published, e.g., en-us
-      --retry-failed=<value>      (optional) Use this option to retry publishing the failed entries from the logfile. It
-                                  is optional. Specify the name of the logfile that lists failed publish calls. If this
-                                  option is used, it will override all other flags.
-      --source-env=<value>        The name of the source environment where the entries were initially published.
-
-DESCRIPTION
-  Publish unpublished entries from the source environment, to other environments and locales
-  The publish-only-unpublished command is used to publish unpublished entries from the source environment, to other
-  environments and locales
-
-  Note: Content type(s), Source Environment, Destination Environment(s) and Source Locale are required to execute the
-  command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-
-ALIASES
-  $ csdx cm:bulk-publish:unpublished-entries
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:publish-only-unpublished -b --content-types [CONTENT TYPES] -e [ENVIRONMENTS] --locales LOCALE -a [MANAGEMENT TOKEN ALIAS] -source-env [SOURCE ENV]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:bulk-publish:configure -a [ALIAS]`
-
-  $ csdx cm:entries:publish-only-unpublished --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:publish-only-unpublished -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed
-
-  $ csdx cm:entries:publish-only-unpublished --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch
-
-  $ csdx cm:entries:publish-only-unpublished -b --content-types [CONTENT TYPES] -e [ENVIRONMENTS] --locales LOCALE -a [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME] -source-env [SOURCE ENV]
-
-
-
-  Using --stack-api-key
-
-  $ csdx cm:entries:publish-only-unpublished -b --content-types [CONTENT TYPES] -e [ENVIRONMENTS] --locales LOCALE -a [MANAGEMENT TOKEN ALIAS] --stack-api-key [STACK API KEY] -source-env [SOURCE ENV]
-```
-
-## `csdx cm:entries:migrate-html-rte`
-
-Migration script to migrate content from HTML RTE to JSON RTE
-
-```
-USAGE
-  $ csdx cm:entries:migrate-html-rte [-c <value>] [-a <value>] [--stack-api-key <value>] [--content-type <value>]
-    [--global-field] [-y] [--branch <value>] [--html-path <value> --json-path <value>] [--delay <value>] [--locale
-    <value>] [--batch-limit <value>]
-
-FLAGS
-  -a, --alias=<value>          Enter the alias name. You must use either the --alias flag or the --stack-api-key flag.
-  -c, --config-path=<value>    Specify the path where your config file is located.
-  -y, --yes                    Avoids reconfirmation of your configuration.
-      --batch-limit=<value>    [default: 50] Provide batch limit for updating entries (default: 50).
-      --branch=<value>         The name of the branch to be used.
-      --content-type=<value>   Specify the UID of the content type for which you want to migrate HTML RTE content.
-      --delay=<value>          [default: 1000] To set the interval time between the migration of HTML RTE to JSON RTE in
-                               subsequent entries of a content type. The default value is 1,000 milliseconds.
-      --global-field           Checks whether the specified UID belongs to a content type or a global field. This flag
-                               is set to false by default.
-      --html-path=<value>      Enter the path to the HTML RTE whose content you want to migrate.
-      --json-path=<value>      Enter the path to the JSON RTE to which you want to migrate the HTML RTE content.
-      --locale=<value>         The locale from which entries will be migrated.
-      --stack-api-key=<value>  API key of the source stack. You must use either the --stack-api-key flag or the --alias
-                               flag.
-
-DESCRIPTION
-  Migration script to migrate content from HTML RTE to JSON RTE
-
-ALIASES
-  $ csdx cm:migrate-rte
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:migrate-html-rte --config-path path/to/config.json
-
-
-
-  Using Flags
-
-  $ csdx cm:entries:migrate-html-rte --alias alias --content-type content_type_uid --html-path html-path --json-path json-path
-
-
-
-  Nested RTE
-
-  $ csdx cm:entries:migrate-html-rte --alias alias --content-type content_type_uid --html-path modular_block_uid.block_uid.html_rte_uid --json-path modular_block_uid.block_uid.json_rte_uid
-
-
-
-  $ csdx cm:entries:migrate-html-rte --alias alias --content-type content_type_uid --html-path group_uid.html_rte_uid --json-path group_uid.json_rte_uid
-
-
-
-  Global Field
-
-  $ csdx cm:entries:migrate-html-rte --alias alias --content-type global_field_uid --global-field --html-path html-path --json-path json-path
-```
-
-_See code: [@contentstack/cli-cm-migrate-rte](https://github.com/contentstack/cli/blob/main/packages/contentstack-migrate-rte/src/commands/cm/entries/migrate-html-rte.js)_
-
-## `csdx cm:entries:publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--publish-all-content-types] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>] [--delivery-token <value>] [--source-env <value>] [--entry-uid <value>] [--include-variants]`
-
-Publish entries from multiple contenttypes to multiple environments and locales
-
-```
-USAGE
-  $ csdx cm:entries:publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--publish-all-content-types]
-    [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>] [--delivery-token
-    <value>] [--source-env <value>] [--entry-uid <value>] [--include-variants]
-
-FLAGS
-  -B, --branch=<value>             [default: main] The name of the branch where you want to perform the bulk publish
-                                   operation. If you don’t mention the branch name, then by default the content from
-                                   main branch will be published.
-  -a, --alias=<value>              Alias (name) of the management token. You must use either the --alias flag or the
-                                   --stack-api-key flag.
-  -c, --config=<value>             (optional) The path of the optional configuration JSON file containing all the
-                                   options for a single run. Refer to the configure command to create a configuration
-                                   file.
-  -e, --environments=<value>...    The name of the environment on which entries will be published. In case of multiple
-                                   environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>      API key of the source stack. You must use either the --stack-api-key flag or the
-                                   --alias flag.
-  -l, --locales=<value>...         Locales in which entries will be published, e.g., en-us. In the case of multiple
-                                   locales, specify the codes separated by spaces.
-  -y, --yes                        Set it to true to process the command with the current configuration.
-      --api-version=<value>        API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-publish=<value>       [default: true] Set this flag to use Contentstack's Bulk Publish APIs. This flag is
-                                   set to true, by default.
-      --content-types=<value>...   The UID of the content type(s) whose entries you want to publish in bulk. In case of
-                                   multiple content types, specify the IDs separated by spaces.
-      --delivery-token=<value>     The delivery token of the source environment.
-      --entry-uid=<value>          Entry Uid for publish all associated variant entries.
-      --include-variants           Include Variants flag will publish all associated variant entries with base entry.
-      --publish-all-content-types  (optional) Set it to true to bulk publish entries from all content types. If the
-                                   --content-types option is already used, then you cannot use this option.
-      --retry-failed=<value>       (optional) Use this option to retry publishing the failed entries/ assets from the
-                                   logfile. Specify the name of the logfile that lists failed publish calls. If this
-                                   option is used, it will override all other flags.
-      --source-env=<value>         Source environment
-
-DESCRIPTION
-  Publish entries from multiple contenttypes to multiple environments and locales
-  The publish command is used to publish entries from the specified content types, to the
-  specified environments and locales
-
-  Note: Content Types, Environments and Locales are required to execute the command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-
-ALIASES
-  $ csdx cm:bulk-publish:entries
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:stacks:publish-configure -a [ALIAS]`
-
-  $ csdx cm:entries:publish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:publish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed
-
-  $ csdx cm:entries:publish --retry-failed [LOG FILE NAME]
-
-  $ csdx cm:entries:publish -r [LOG FILE NAME]
-
-
-
-  Using --branch
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME]
-
-
-
-  Using --source-env
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS] --source-env [SOURCE ENVIRONMENT] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --stack-api-key
-
-  $ csdx cm:entries:publish -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] --stack-api-key [STACK API KEY] --source-env [SOURCE ENVIRONMENT] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --include-variants
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] --stack-api-key [STACK API KEY] --source-env [SOURCE ENVIRONMENT] --delivery-token [DELIVERY TOKEN] [--include-variants]
-
-
-
-  Using --entry-uid and --include-variants
-
-  $ csdx cm:entries:publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] --stack-api-key [STACK API KEY] --source-env [SOURCE ENVIRONMENT] --delivery-token [DELIVERY TOKEN] --entry-uid [ENTRY UID] [--include-variants]
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/entries/publish.js)_
-
-## `csdx cm:entries:publish-modified [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]`
-
-Publish edited entries from a specified content type to the given locales and environments
-
-```
-USAGE
-  $ csdx cm:entries:publish-modified [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>]
-    [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]
-
-FLAGS
-  -B, --branch=<value>            [default: main] The name of the branch where you want to perform the bulk publish
-                                  operation. If you don't mention the branch name, then by default the entries from main
-                                  branch will be published.
-  -a, --alias=<value>             Alias (name) of the management token. You must use either the --alias flag or the
-                                  --stack-api-key flag.
-  -c, --config=<value>            (optional) The path of the optional configuration JSON file containing all the options
-                                  for a single run. Refer to the configure command to create a configuration file.
-  -e, --environments=<value>...   The name of the environment(s) on which the entries will be published. In case of
-                                  multiple environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>     API key of the source stack. You must use either the --stack-api-key flag or the
-                                  --alias flag.
-  -l, --locales=<value>...        Locales in which entries will be published, e.g., en-us. In the case of multiple
-                                  locales, specify the codes separated by spaces.
-  -y, --yes                       Set it to true to process the command with the current configuration.
-      --api-version=<value>       API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-publish=<value>      [default: true] Set this flag to use Contentstack's Bulk Publish APIs. It is true, by
-                                  default.
-      --content-types=<value>...  The UID of the content type(s) whose edited entries you want to publish in bulk. In
-                                  case of multiple content types, specify the IDs separated by spaces.
-      --retry-failed=<value>      (optional) Use this option to retry publishing the failed entries/assets from the
-                                  logfile. Specify the name of the logfile that lists failed publish calls. If this
-                                  option is used, it will override all other flags
-      --source-env=<value>        The name of the source environment where the entries were initially published.
-
-DESCRIPTION
-  Publish edited entries from a specified content type to the given locales and environments
-  The publish-modified command is used to publish entries from the specified content types, to the
-  specified environments and locales
-
-  Note: Content type(s), Source Environment, Destination Environment(s) and Locale(s) are required to execute the
-  command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-
-ALIASES
-  $ csdx cm:bulk-publish:entry-edits
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:publish-modified --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --source-env [SOURCE_ENV] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:stacks:publish-configure -a [ALIAS]`
-
-  $ csdx cm:entries:publish-modified --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:publish-modified -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed
-
-  $ csdx cm:entries:publish-modified --retry-failed [LOG FILE NAME]
-
-  $ csdx cm:entries:publish-modified -r [LOG FILE NAME]
-
-
-
-  Using --branch
-
-  $ csdx cm:entries:publish-modified --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --source-env [SOURCE_ENV] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key
-
-  $ csdx cm:entries:publish-modified --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --source-env [SOURCE_ENV] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -stack-api-key [STACK API KEY]
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/entries/publish-modified.js)_
-
-## `csdx cm:entries:publish-non-localized-fields [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]`
-
-Publish non-localized fields for the given content types, from a particular source environment to the specified environments
-
-```
-USAGE
-  $ csdx cm:entries:publish-non-localized-fields [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>]
-    [--content-types <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]
-
-FLAGS
-  -B, --branch=<value>            [default: main] The name of the branch where you want to perform the bulk publish
-                                  operation. If you don’t mention the branch name, then by default the content from the
-                                  main branch will be published.
-  -a, --alias=<value>             Alias (name) of the management token. You must use either the --alias flag or the
-                                  --stack-api-key flag.
-  -c, --config=<value>            (optional) The path of the optional configuration JSON file containing all the options
-                                  for a single run. Refer to the configure command to create a configuration file.
-  -e, --environments=<value>...   The name of the environment on which entries will be published. In case of multiple
-                                  environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>     API key of the source stack. You must use either the --stack-api-key flag or the
-                                  --alias flag.
-  -y, --yes                       Set it to true to process the command with the current configuration.
-      --api-version=<value>       API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-publish=<value>      [default: true] Set this flag to use Contentstack’s Bulk Publish APIs. It is true, by
-                                  default.
-      --content-types=<value>...  The UID of the content type whose entries you want to publish in bulk. In case of
-                                  multiple content types, specify their IDs separated by spaces.
-      --retry-failed=<value>      Use this option to retry publishing the failed entries from the logfile. Specify the
-                                  name of the logfile that lists failed publish calls. If this option is used, it will
-                                  override all other flags.
-      --source-env=<value>        The name of the source environment.
-
-DESCRIPTION
-  Publish non-localized fields for the given content types, from a particular source environment to the specified
-  environments
-  The non-localized field changes command is used to publish non-localized field changes from the given content types to
-  the specified environments
-
-  Note: Content types, Environments and Source Environment are required to execute this command successfully.
-  But, if retryFailed flag is set, then only a logfile is required
-
-ALIASES
-  $ csdx cm:bulk-publish:nonlocalized-field-changes
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:publish-non-localized-fields --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --alias [MANAGEMENT TOKEN ALIAS] --source-env [SOURCE ENV]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:bulk-publish:configure -a [ALIAS]`
-
-  $ csdx cm:entries:publish-non-localized-fields --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:publish-non-localized-fields -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed flag
-
-  $ csdx cm:entries:publish-non-localized-fields --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch flag
-
-  $ csdx cm:entries:publish-non-localized-fields --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --alias [MANAGEMENT TOKEN ALIAS] --source-env [SOURCE ENV] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key flag
-
-  $ csdx cm:entries:publish-non-localized-fields --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --stack-api-key [STACK API KEY] --source-env [SOURCE ENV]
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/entries/publish-non-localized-fields.js)_
-
-## `csdx cm:entries:publish-only-unpublished [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>] [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]`
-
-Publish unpublished entries from the source environment, to other environments and locales
-
-```
-USAGE
-  $ csdx cm:entries:publish-only-unpublished [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--source-env <value>]
-    [--content-types <value>] [--locales <value>] [-e <value>] [-c <value>] [-y] [--branch <value>]
-
-FLAGS
-  -B, --branch=<value>            [default: main] The name of the branch where you want to perform the bulk publish
-                                  operation. If you don't mention the branch name, then by default the entries from main
-                                  branch will be published.
-  -a, --alias=<value>             Alias (name) of the management token. You must use either the --alias flag or the
-                                  --stack-api-key flag.
-  -b, --bulk-publish=<value>      [default: true] Set this flag to use Contentstack's Bulk Publish APIs. It is true, by
-                                  default.
-  -c, --config=<value>            (optional)  The path of the optional configuration JSON file containing all the
-                                  options for a single run. Refer to the configure command to create a configuration
-                                  file.
-  -e, --environments=<value>...   The name of the environment on which entries will be published. In case of multiple
-                                  environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>     API key of the source stack. You must use either the --stack-api-key flag or the
-                                  --alias flag.
-  -y, --yes                       Set it to true to process the command with the current configuration.
-      --api-version=<value>       API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2]..
-      --content-types=<value>...  The UID of the content type(s) whose entries you want to publish in bulk. In case of
-                                  multiple content types, specify their IDs separated by spaces.
-      --locales=<value>           Locale in which entries will be published, e.g., en-us
-      --retry-failed=<value>      (optional) Use this option to retry publishing the failed entries from the logfile. It
-                                  is optional. Specify the name of the logfile that lists failed publish calls. If this
-                                  option is used, it will override all other flags.
-      --source-env=<value>        The name of the source environment where the entries were initially published.
-
-DESCRIPTION
-  Publish unpublished entries from the source environment, to other environments and locales
-  The publish-only-unpublished command is used to publish unpublished entries from the source environment, to other
-  environments and locales
-
-  Note: Content type(s), Source Environment, Destination Environment(s) and Source Locale are required to execute the
-  command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-
-ALIASES
-  $ csdx cm:bulk-publish:unpublished-entries
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:publish-only-unpublished -b --content-types [CONTENT TYPES] -e [ENVIRONMENTS] --locales LOCALE -a [MANAGEMENT TOKEN ALIAS] -source-env [SOURCE ENV]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:bulk-publish:configure -a [ALIAS]`
-
-  $ csdx cm:entries:publish-only-unpublished --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:publish-only-unpublished -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed
-
-  $ csdx cm:entries:publish-only-unpublished --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch
-
-  $ csdx cm:entries:publish-only-unpublished -b --content-types [CONTENT TYPES] -e [ENVIRONMENTS] --locales LOCALE -a [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME] -source-env [SOURCE ENV]
-
-
-
-  Using --stack-api-key
-
-  $ csdx cm:entries:publish-only-unpublished -b --content-types [CONTENT TYPES] -e [ENVIRONMENTS] --locales LOCALE -a [MANAGEMENT TOKEN ALIAS] --stack-api-key [STACK API KEY] -source-env [SOURCE ENV]
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/entries/publish-only-unpublished.js)_
-
-## `csdx cm:entries:unpublish`
-
-Unpublish entries from the given environment
-
-```
-USAGE
-  $ csdx cm:entries:unpublish [-a <value>] [-k <value>] [-e <value>] [-c <value>] [-y] [--locale <value>] [--branch
-    <value>] [--retry-failed <value>] [--bulk-unpublish <value>] [--api-version <value>] [--content-type <value>]
-    [--delivery-token <value>] [--include-variants]
-
-FLAGS
-  -a, --alias=<value>           Alias (name) for the management token. You must use either the --alias flag or the
-                                --stack-api-key flag.
-  -c, --config=<value>          (optional) Path to the configuration JSON file containing all options for a single run.
-                                Refer to the configure command to create a configuration file.
-  -e, --environment=<value>     The name of the environment from where entries/assets need to be unpublished.
-  -k, --stack-api-key=<value>   API key of the source stack. You must use either the --stack-api-key flag or the --alias
-                                flag.
-  -y, --yes                     Set to true to process the command with the current configuration.
-      --api-version=<value>     API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --branch=<value>          [default: main] Specify the branch to fetch the content. If not mentioned, the main
-                                branch will be used by default.
-      --bulk-unpublish=<value>  [default: true] This flag is set to true by default. It indicates that Contentstack's
-                                Bulk Publish APIs will be used to unpublish the entries.
-      --content-type=<value>    The UID of the content type whose entries you want to unpublish in bulk.
-      --delivery-token=<value>  The delivery token of the source environment.
-      --include-variants        Include Variants flag will unpublish all associated variant entries.
-      --locale=<value>          Locale from which entries/assets will be unpublished, e.g., en-us.
-      --retry-failed=<value>    (optional) Use this option to retry unpublishing the failed entries from the logfile.
-                                Specify the name of the logfile that lists failed unpublish calls. If used, this option
-                                will override all other flags.
-
-DESCRIPTION
-  Unpublish entries from the given environment
-  The unpublish command is used to unpublish entries from the given environment
-
-  Note: Environment (Source Environment) and Locale are required to execute the command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:stacks:unpublish --bulk-unpublish --content-type [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:bulk-publish:configure --alias [ALIAS]`
-
-  $ csdx cm:stacks:unpublish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:stacks:unpublish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed flag
-
-  $ csdx cm:stacks:unpublish --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch flag
-
-  $ csdx cm:stacks:unpublish --bulk-unpublish --content-type [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] --delivery-token [DELIVERY TOKEN] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key flag
-
-  $ csdx cm:stacks:unpublish --bulk-unpublish --content-type [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --stack-api-key [STACK API KEY] --delivery-token [DELIVERY TOKEN]
-
-
-
-  Using --include-variants flag
-
-  $ csdx cm:stacks:unpublish --bulk-unpublish --content-type [CONTENT TYPE] --environment [SOURCE ENV] --locale [LOCALE] --stack-api-key [STACK API KEY] --delivery-token [DELIVERY TOKEN] --include-variants
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/entries/unpublish.js)_
-
-## `csdx cm:entries:update-and-publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--content-types <value>] [-t <value>] [-e <value>] [-c <value>] [-y] [--locales <value>] [--branch <value>]`
-
-Add fields from updated content types to their respective entries
-
-```
-USAGE
-  $ csdx cm:entries:update-and-publish [-a <value>] [--retry-failed <value>] [--bulk-publish <value>] [--content-types <value>] [-t
-    <value>] [-e <value>] [-c <value>] [-y] [--locales <value>] [--branch <value>]
-
-FLAGS
-  -B, --branch=<value>            [default: main] The name of the branch where you want to perform the bulk publish
-                                  operation. If you don’t mention the branch name, then by default the content from the
-                                  main branch will be published.
-  -a, --alias=<value>             Alias (name) of the management token. You must use either the --alias flag or the
-                                  --stack-api-key flag.
-  -c, --config=<value>            (optional) The path of the optional configuration JSON file containing all the options
-                                  for a single run. Refer to the configure command to create a configuration file.
-  -e, --environments=<value>...   The name of the environment on which entries will be published. In case of multiple
-                                  environments, specify their names separated by spaces.
-  -k, --stack-api-key=<value>     API key of the source stack. You must use either the --stack-api-key flag or the
-                                  --alias flag.
-  -l, --locales=<value>...        Locales in which entries will be published, e.g., en-us. In the case of multiple
-                                  locales, specify the codes separated by spaces.
-  -t, --contentTypes=<value>...   The Contenttypes from which entries will be published.
-  -y, --yes                       Set it to true to process the command with the current configuration.
-      --api-version=<value>       API version to be used. Values [Default: 3, Nested Reference Publishing: 3.2].
-      --bulk-publish=<value>      [default: true] Set this flag to use Contentstack’s Bulk Publish APIs. It is true, by
-                                  default.
-      --content-types=<value>...  The UID of the content type ID whose entries you want to publish in bulk. In case of
-                                  multiple content types, specify their IDs separated by spaces.
-      --force                     Update and publish all entries even if no fields have been added.
-      --retry-failed=<value>      Use this option to retry publishing the failed entries from the logfile. Specify the
-                                  name of the logfile that lists failed publish calls. If this option is used, it will
-                                  override all other flags.
-
-DESCRIPTION
-  Add fields from updated content types to their respective entries
-  The update-and-publish command is used to update existing entries with the updated schema of the respective content
-  type
-
-  Note: Content types, Environments and Locales are required to execute the command successfully
-  But, if retry-failed flag is set, then only a logfile is required
-
-
-ALIASES
-  $ csdx cm:bulk-publish:add-fields
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:entries:update-and-publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file at the current working directory using `csdx cm:stacks:publish-configure -a [ALIAS]`
-
-  $ csdx cm:entries:update-and-publish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:entries:update-and-publish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed
-
-  $ csdx cm:entries:update-and-publish --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch
-
-  $ csdx cm:entries:update-and-publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] -a [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME]
-
-
-
-  Using --stack-api-key
+  $ csdx cm:branches:create --source main -uid new_branch -k bltxxxxxxxx
 
-  $ csdx cm:entries:update-and-publish --content-types [CONTENT TYPE 1] [CONTENT TYPE 2] -e [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE 1] [LOCALE 2] --stack-api-key [STACK API KEY]
+  $ csdx cm:branches:create --source main --uid new_branch --stack-api-key bltxxxxxxxx
 ```
 
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/entries/update-and-publish.js)_
+_See code: [@contentstack/cli-cm-branches](https://github.com/contentstack/cli/blob/main/packages/contentstack-export/src/commands/cm/branches/create.ts)_
 
-## `csdx cm:stacks:export [-c <value>] [-k <value>] [-d <value>] [-a <value>] [--module <value>] [--content-types <value>] [--branch <value>] [--secured-assets]`
+## `csdx cm:branches:delete [-uid <value>] [-k <value>]`
 
-Export content from a stack
+Delete a branch
 
 ```
 USAGE
-  $ csdx cm:export cm:stacks:export [-c <value>] [-k <value>] [-d <value>] [-a <value>] [--module <value>]
-    [--content-types <value>] [--branch <value>] [--secured-assets]
+  $ csdx cm:branches:delete [-uid <value>] [-k <value>]
+  $ csdx cm:branches:delete [--uid <value>] [--stack-api-key <value>]
 
 FLAGS
-  -B, --branch=<value>            [optional] The name of the branch where you want to export your content. If you don't
-                                  mention the branch name, then by default the content will be exported from all the
-                                  branches of your stack.
-  -a, --alias=<value>             The management token alias of the source stack from which you will export content.
-  -c, --config=<value>            [optional] Path of the config
-  -d, --data-dir=<value>          The path or the location in your file system to store the exported content. For e.g.,
-                                  ./content
-  -k, --stack-api-key=<value>     API Key of the source stack
-  -m, --module=<value>            [optional] Specific module name. If not specified, the export command will export all
-                                  the modules to the stack. The available modules are assets, content-types, entries,
-                                  environments, extensions, marketplace-apps, global-fields, labels, locales, webhooks,
-                                  workflows, custom-roles, taxonomies, and studio.
-  -t, --content-types=<value>...  [optional]  The UID of the content type(s) whose content you want to export. In case
-                                  of multiple content types, specify the IDs separated by spaces.
-  -y, --yes                       [optional] Force override all Marketplace prompts.
-      --branch-alias=<value>      (Optional) The alias of the branch from which you want to export content.
-      --secured-assets            [optional] Use this flag for assets that are secured.
+  -k, --stack-api-key=<value>  Stack API key
+  -y, --yes                    Force the deletion of the branch by skipping the confirmation
+      --uid=<value>            Branch UID to be deleted
 
 DESCRIPTION
-  Export content from a stack
-
-ALIASES
-  $ csdx cm:export
+  Delete a branch
 
 EXAMPLES
-  $ csdx cm:stacks:export --stack-api-key <stack_api_key> --data-dir <path/of/export/destination/dir>
-
-  $ csdx cm:stacks:export --config <path/to/config/dir>
-
-  $ csdx cm:stacks:export --alias <management_token_alias>
-
-  $ csdx cm:stacks:export --alias <management_token_alias> --data-dir <path/to/export/destination/dir>
+  $ csdx cm:branches:delete
 
-  $ csdx cm:stacks:export --alias <management_token_alias> --config <path/to/config/file>
+  $ csdx cm:branches:delete --uid main -k bltxxxxxxxx
 
-  $ csdx cm:stacks:export --module <single module name>
+  $ csdx cm:branches:delete --uid main --stack-api-key bltxxxxxxxx
 
-  $ csdx cm:stacks:export --branch [optional] branch name
+  $ csdx cm:branches:delete --uid main --stack-api-key bltxxxxxxxx --yes
 ```
 
->>>>>>> development
-## `csdx cm:export-to-csv`
+_See code: [@contentstack/cli-cm-branches](https://github.com/contentstack/cli/blob/main/packages/contentstack-export/src/commands/cm/branches/delete.ts)_
+
+## `csdx cm:branches:diff [--base-branch <value>] [--compare-branch <value>] [-k <value>][--module <value>] [--format <value>] [--csv-path <value>]`
 
-Export entries, taxonomies, terms or organization users to csv using this command
+Differences between two branches
 
 ```
 USAGE
-  $ csdx cm:export-to-csv [--action entries|users|teams|taxonomies] [-a <value>] [--org <value>] [-n <value>] [-k
-    <value>] [--org-name <value>] [--locale <value>] [--content-type <value>] [--branch <value>] [--team-uid <value>]
-    [--taxonomy-uid <value>] [--include-fallback] [--fallback-locale <value>] [--delimiter <value>]
+  $ csdx cm:branches:diff [--base-branch <value>] [--compare-branch <value>] [-k <value>][--module <value>] [--format
+    <value>] [--csv-path <value>]
 
 FLAGS
-  -a, --alias=<value>            Alias of the management token.
-  -k, --stack-api-key=<value>    API Key of the source stack.
-  -n, --stack-name=<value>       Name of the stack that needs to be created as CSV filename.
-      --action=<option>          Option to export data (entries, users, teams, taxonomies). <options:
-                                 entries|users|teams|taxonomies>
-                                 <options: entries|users|teams|taxonomies>
-      --branch=<value>           Branch from which entries will be exported.
-      --content-type=<value>     Content type of entries that will be exported.
-      --delimiter=<value>        [default: ,] [optional] Provide a delimiter to separate individual data fields within
-                                 the CSV file. For example: cm:export-to-csv --delimiter '|'
-      --fallback-locale=<value>  [Optional] Specify a specific fallback locale for taxonomy export. This locale will be
-                                 used when a taxonomy term doesn't exist in the primary locale. Takes priority over
-                                 branch fallback hierarchy when both are specified.
-      --include-fallback         [Optional] Include fallback locale data when exporting taxonomies. When enabled, if a
-                                 taxonomy term doesn't exist in the specified locale, it will fallback to the hierarchy
-                                 defined in the branch settings.
-      --locale=<value>           Locale of entries that will be exported.
-      --org=<value>              Provide organization UID to clone org users.
-      --org-name=<value>         Name of the organization that needs to be created as CSV filename.
-      --taxonomy-uid=<value>     Provide the taxonomy UID of the related terms you want to export.
-      --team-uid=<value>         Provide the UID of a specific team in an organization.
+  -k, --stack-api-key=<value>   [optional] Provide the stack API key to show the difference between branches.
+      --base-branch=<value>     [optional] Base branch (Target branch).
+      --compare-branch=<value>  [optional] Compare branch (Source branch).
+      --csv-path=<value>        [optional] Custom path for CSV output file. If not provided, will use the current
+                                working directory.
+      --format=<option>         [default: compact-text] [default: compact-text] [optional] Type of flags to show the
+                                difference between two branches. <options: compact-text, detailed-text>
+                                <options: compact-text|detailed-text>
+      --module=<option>         [optional] Module. <options: content-types, global-fields, all>
+                                <options: content-types|global-fields|all>
 
 DESCRIPTION
-  Export entries, taxonomies, terms or organization users to csv using this command
-
-ALIASES
-  $ csdx cm:export-to-csv
+  Differences between two branches
 
 EXAMPLES
-  $ csdx cm:export-to-csv
+  $ csdx cm:branches:diff
+
+  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx"
+
+  $ csdx cm:branches:diff --compare-branch "develop"
 
+  $ csdx cm:branches:diff --compare-branch "develop" --stack-api-key "bltxxxxxxxx"
 
+  $ csdx cm:branches:diff --compare-branch "develop" --module "content-types"
 
-  Exporting entries to CSV
+  $ csdx cm:branches:diff --module "content-types" --format "detailed-text"
 
-  $ csdx cm:export-to-csv --action entries --locale <locale> --alias <management-token-alias> --content-type <content-type>
+  $ csdx cm:branches:diff --compare-branch "develop" --format "detailed-text"
 
+  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main"
 
+  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main" --compare-branch "develop"
 
-  Exporting entries to CSV with stack name and branch
+  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main" --module "content-types"
 
-  $ csdx cm:export-to-csv --action entries --locale <locale> --alias <management-token-alias> --content-type <content-type> --stack-name <stack-name> --branch <branch-name>
+  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main" --compare-branch "develop" --module "content-types"
 
+  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main" --compare-branch "develop" --module "content-types" --format "detailed-text"
 
+  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main" --compare-branch "develop" --module "content-types" --format "compact-text"
 
-  Exporting organization users to CSV
+  $ csdx cm:branches:diff --stack-api-key "bltxxxxxxxx" --base-branch "main" --compare-branch "develop" --module "content-types" --format "detailed-text" --csv-path "./reports/diff-report.csv"
+```
 
-  $ csdx cm:export-to-csv --action users --org <org-uid>
+_See code: [@contentstack/cli-cm-branches](https://github.com/contentstack/cli/blob/main/packages/contentstack-export/src/commands/cm/branches/diff.ts)_
 
+## `csdx cm:branches:merge [-k <value>][--compare-branch <value>] [--no-revert] [--export-summary-path <value>] [--use-merge-summary <value>] [--comment <value>] [--base-branch <value>]`
 
+Merge changes from a branch
 
-  Exporting organization teams to CSV
+```
+USAGE
+  $ csdx cm:branches:merge [-k <value>][--compare-branch <value>] [--no-revert] [--export-summary-path <value>]
+    [--use-merge-summary <value>] [--comment <value>] [--base-branch <value>]
 
-  $ csdx cm:export-to-csv --action teams --org <org-uid>
+FLAGS
+  -k, --stack-api-key=<value>        [optional] Provide stack API key to show the difference between the branches.
+      --base-branch=<value>          [optional] Base branch (Target branch).
+      --comment=<value>              [optional] Pass a comment.
+      --compare-branch=<value>       [optional] Compare branch (Source branch).
+      --export-summary-path=<value>  [optional] Export summary file path.
+      --no-revert                    [optional] If passed, will not create the new revert branch.
+      --use-merge-summary=<value>    [optional] Path of merge summary file.
 
+DESCRIPTION
+  Merge changes from a branch
 
+EXAMPLES
+  $ csdx cm:branches:merge --stack-api-key bltxxxxxxxx --compare-branch feature-branch
 
-  Exporting teams with specific team UID
+  $ csdx cm:branches:merge --stack-api-key bltxxxxxxxx --comment "merge comment"
 
-  $ csdx cm:export-to-csv --action teams --org <org-uid> --team-uid <team-uid>
+  $ csdx cm:branches:merge -k bltxxxxxxxx --base-branch base-branch
 
+  $ csdx cm:branches:merge --export-summary-path file/path
 
+  $ csdx cm:branches:merge --use-merge-summary file-path
 
-  Exporting taxonomies to CSV
+  $ csdx cm:branches:merge -k bltxxxxxxxx --no-revert
 
-  $ csdx cm:export-to-csv --action taxonomies --alias <management-token-alias>
+  $ csdx cm:branches:merge -k bltxxxxxxxx --compare-branch feature-branch --no-revert
+```
 
+_See code: [@contentstack/cli-cm-branches](https://github.com/contentstack/cli/blob/main/packages/contentstack-export/src/commands/cm/branches/merge.ts)_
 
+## `csdx cm:branches:merge-status -k <value> --merge-uid <value>`
 
-  Exporting specific taxonomy with locale
+Check the status of a branch merge job
 
-  $ csdx cm:export-to-csv --action taxonomies --alias <management-token-alias> --taxonomy-uid <taxonomy-uid> --locale <locale>
+```
+USAGE
+  $ csdx cm:branches:merge-status -k <value> --merge-uid <value>
 
+FLAGS
+  -k, --stack-api-key=<value>  (required) Provide your stack API key.
+      --merge-uid=<value>      (required) Merge job UID to check status for.
 
+DESCRIPTION
+  Check the status of a branch merge job
 
-  Exporting taxonomies with fallback locale
+EXAMPLES
+  $ csdx cm:branches:merge-status -k bltxxxxxxxx --merge-uid merge_abc123
 
-  $ csdx cm:export-to-csv --action taxonomies --alias <management-token-alias> --locale <locale> --include-fallback --fallback-locale <fallback-locale>
+  $ csdx cm:branches:merge-status --stack-api-key bltxxxxxxxx --merge-uid merge_abc123
 ```
 
-_See code: [@contentstack/cli-cm-export-to-csv](https://github.com/contentstack/cli/blob/main/packages/contentstack-export-to-csv/src/commands/cm/export-to-csv.ts)_
+_See code: [@contentstack/cli-cm-branches](https://github.com/contentstack/cli/blob/main/packages/contentstack-export/src/commands/cm/branches/merge-status.ts)_
 
 ## `csdx cm:stacks:migration [-k <value>] [-a <value>] [--file-path <value>] [--branch <value>] [--config-file <value>] [--config <value>] [--multiple]`
 
@@ -2099,43 +553,7 @@ EXAMPLES
 
   $ csdx cm:migration --multiple --file-path <migration/scripts/dir/path> 
 
-  $ csdx cm:migration --alias --file-path <migration/script/file/path> -k <api-key>
-```
-
-## `csdx cm:stacks:seed [--repo <value>] [--org <value>] [-k <value>] [-n <value>] [-y <value>] [-s <value>] [--locale <value>]`
-
-Create a stack from existing content types, entries, assets, etc
-
-```
-USAGE
-  $ csdx cm:seed cm:stacks:seed [--repo <value>] [--org <value>] [-k <value>] [-n <value>] [-y <value>] [-s
-    <value>] [--locale <value>]
-
-FLAGS
-  -a, --alias=<value>          Alias of the management token
-  -k, --stack-api-key=<value>  Provide stack API key to seed content to
-  -n, --stack-name=<value>     Name of a new stack that needs to be created.
-  -o, --org=<value>            Provide Organization UID to create a new stack
-  -r, --repo=<value>           GitHub organization name or GitHub user name/repository name.
-  -s, --stack=<value>          Provide the stack UID to seed content.
-  -y, --yes=<value>            [Optional] Skip the stack confirmation.
-
-DESCRIPTION
-  Create a stack from existing content types, entries, assets, etc
-
-ALIASES
-  $ csdx cm:seed
-
-EXAMPLES
-  $ csdx cm:stacks:seed
-
-  $ csdx cm:stacks:seed --repo "account"
-
-  $ csdx cm:stacks:seed --repo "account/repository"
-
-  $ csdx cm:stacks:seed --repo "account/repository" --stack-api-key "stack-api-key" //seed content into specific stack
-
-  $ csdx cm:stacks:seed --repo "account/repository" --org "your-org-uid" --stack-name "stack-name" //create a new stack in given org uid
+  $ csdx cm:migration --alias <management-token-alias> --file-path <migration/script/file/path>
 ```
 
 ## `csdx cm:stacks:clone [--source-branch <value>] [--target-branch <value>] [--source-management-token-alias <value>] [--destination-management-token-alias <value>] [-n <value>] [--type a|b] [--source-stack-api-key <value>] [--destination-stack-api-key <value>] [--import-webhook-status disable|current]`
@@ -2193,111 +611,6 @@ EXAMPLES
   $ csdx cm:stacks:clone --source-branch --target-branch --source-management-token-alias <management token alias> --destination-management-token-alias <management token alias> --type <value a or b>
 ```
 
-## `csdx cm:stacks:audit`
-
-Perform audits and find possible errors in the exported Contentstack data
-
-```
-USAGE
-  $ csdx cm:stacks:audit [-c <value>] [-d <value>] [--show-console-output] [--report-path <value>] [--modules
-    content-types|global-fields|entries|extensions|workflows|custom-roles|assets|field-rules|composable-studio...]
-    [--columns <value>] [--sort <value>] [--filter <value>] [--csv] [--no-truncate] [--no-header] [--output
-    csv|json|yaml]
-
-FLAGS
-  --modules=<option>...  Provide the list of modules to be audited
-                         <options: content-types|global-fields|entries|extensions|workflows|custom-roles|assets|field-ru
-                         les|composable-studio>
-  --report-path=<value>  Path to store the audit reports
-
-COMMON FLAGS
-  -c, --config=<value>       Path of the external config
-  -d, --data-dir=<value>     Path where the data is stored
-      --show-console-output  Display the audit and audit fix result for individual modules
-
-TABLE FLAGS
-  --columns=<value>  Specify columns to display, comma-separated.
-  --csv              Output results in CSV format.
-  --filter=<value>   Filter rows by a column value (e.g., name=foo).
-  --no-header        Hide table headers in output.
-  --no-truncate      Prevent truncation of long text in columns.
-  --output=<option>  Specify output format: csv, json, or yaml.
-                     <options: csv|json|yaml>
-  --sort=<value>     Sort the table by a column. Use "-" for descending.
-
-DESCRIPTION
-  Perform audits and find possible errors in the exported Contentstack data
-
-EXAMPLES
-  $ csdx cm:stacks:audit
-
-  $ csdx cm:stacks:audit --report-path=<path>
-
-  $ csdx cm:stacks:audit --report-path=<path> --csv
-
-  $ csdx cm:stacks:audit --report-path=<path> --filter="name=<filter-value>"
-
-  $ csdx cm:stacks:audit --report-path=<path> --modules=content-types --filter="name="<filter-value>"
-```
-
-_See code: [@contentstack/cli-audit](https://github.com/contentstack/audit/blob/main/packages/contentstack-audit/src/commands/cm/stacks/audit/index.ts)_
-
-## `csdx cm:stacks:audit:fix`
-
-Perform audits and fix possible errors in the exported Contentstack data.
-
-```
-USAGE
-  $ csdx cm:stacks:audit:fix [-c <value>] [-d <value>] [--show-console-output] [--report-path <value>] [--modules
-    content-types|global-fields|entries|extensions|workflows|custom-roles|assets|field-rules|composable-studio...]
-    [--copy-path <value> --copy-dir] [--fix-only
-    reference|global_field|json:rte|json:extension|blocks|group|content_types...] [--columns <value>] [--sort <value>]
-    [--filter <value>] [--csv] [--no-truncate] [--no-header] [--output csv|json|yaml]
-
-FLAGS
-  --copy-dir              Create backup from the original data.
-  --copy-path=<value>     Provide the path to backup the copied data
-  --fix-only=<option>...  Provide the list of fix options
-                          <options: reference|global_field|json:rte|json:extension|blocks|group|content_types>
-  --modules=<option>...   Provide the list of modules to be audited
-                          <options: content-types|global-fields|entries|extensions|workflows|custom-roles|assets|field-r
-                          ules|composable-studio>
-  --report-path=<value>   Path to store the audit reports
-
-COMMON FLAGS
-  -c, --config=<value>       Path of the external config
-  -d, --data-dir=<value>     Path where the data is stored
-      --show-console-output  Display the audit and audit fix result for individual modules
-
-TABLE FLAGS
-  --columns=<value>  Specify columns to display, comma-separated.
-  --csv              Output results in CSV format.
-  --filter=<value>   Filter rows by a column value (e.g., name=foo).
-  --no-header        Hide table headers in output.
-  --no-truncate      Prevent truncation of long text in columns.
-  --output=<option>  Specify output format: csv, json, or yaml.
-                     <options: csv|json|yaml>
-  --sort=<value>     Sort the table by a column. Use "-" for descending.
-
-DESCRIPTION
-  Perform audits and fix possible errors in the exported Contentstack data.
-
-EXAMPLES
-  $ csdx cm:stacks:audit:fix --copy-dir
-
-  $ csdx cm:stacks:audit:fix --report-path=<path> --copy-dir
-
-  $ csdx cm:stacks:audit:fix --report-path=<path> --copy-dir --csv
-
-  $ csdx cm:stacks:audit:fix --fix-only=reference,global_field --copy-dir
-
-  $ csdx cm:stacks:audit:fix --report-path=<path> --filter="name=<filter-value>"
-
-  $ csdx cm:stacks:audit:fix --report-path=<path> --modules=content-types --filter="name="<filter-value>" --copy-dir --copy-path=<path>
-```
-
-_See code: [@contentstack/cli-audit](https://github.com/contentstack/audit/blob/main/packages/contentstack-audit/src/commands/cm/stacks/audit/fix.ts)_
-
 ## `csdx cm:stacks:bulk-assets`
 
 Bulk operations for assets (publish/unpublish/cross-publish)
@@ -2723,117 +1036,27 @@ EXAMPLES
 
   $ csdx cm:migration --multiple --file-path <migration/scripts/dir/path> 
 
-  $ csdx cm:migration --alias --file-path <migration/script/file/path> -k <api-key>
-```
-
-_See code: [@contentstack/cli-migration](https://github.com/contentstack/cli/blob/main/packages/contentstack-migration/src/commands/cm/stacks/migration.js)_
-
-## `csdx cm:stacks:publish`
-
-Publish entries and assets to multiple environments and locales
-
-```
-USAGE
-  $ csdx cm:stacks:publish
-
-DESCRIPTION
-  Publish entries and assets to multiple environments and locales
-  The publish command is used to publish entries and assets, to the specified environments and locales.
-
-  Note: Content types, Environments and Locales are required to execute the publish entries command successfully.
-  Note: Environments and Locales are required to execute the publish assets command successfully.
-  But, if retry-failed flag is set, then only a logfile is required
-
-EXAMPLES
-  General Usage
-
-  $ csdx cm:stacks:publish --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE] --alias [MANAGEMENT TOKEN ALIAS]
-
-
-
-  Using --config or -c flag
-
-  Generate a config file in the current working directory using `csdx cm:stacks:publish-configure -a [ALIAS]`
-
-  $ csdx cm:stacks:publish --config [PATH TO CONFIG FILE]
-
-  $ csdx cm:stacks:publish -c [PATH TO CONFIG FILE]
-
-
-
-  Using --retry-failed flag
-
-  $ csdx cm:stacks:publish --retry-failed [LOG FILE NAME]
-
-
-
-  Using --branch flag
-
-  $ csdx cm:stacks:publish --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] --branch [BRANCH NAME]
-
-
-
-  Using --api-version flag
-
-  $ csdx cm:stacks:publish --environments [ENVIRONMENT 1] [ENVIRONMENT 2] --locales [LOCALE] --alias [MANAGEMENT TOKEN ALIAS] --api-version [API VERSION]
+  $ csdx cm:migration --alias <management-token-alias> --file-path <migration/script/file/path>
 ```
 
 _See code: [@contentstack/cli-migration](https://github.com/contentstack/cli/blob/main/packages/contentstack-migration/src/commands/cm/stacks/migration.ts)_
 
-## `csdx cm:stacks:publish-revert`
-
-Revert publish operations by using a log file
-
-```
-USAGE
-  $ csdx cm:stacks:publish-revert [--retry-failed <value>] [--log-file <value>]
-
-FLAGS
-  --log-file=<value>      Path of the success logfile of a particular publish action.
-  --retry-failed=<value>  (optional)  Use this option to retry publishing the failed entries from the logfile. Specify
-                          the name of the logfile that lists failed publish calls. If this option is used, it will
-                          override all other flags.
-
-DESCRIPTION
-  Revert publish operations by using a log file
-  The revert command is used to revert all publish operations performed using bulk-publish script.
-  A log file name is required to execute revert command
-
-
-ALIASES
-  $ csdx cm:bulk-publish:revert
-
-EXAMPLES
-  Using --log-file
-
-  cm:bulk-publish:revert --log-file [LOG FILE NAME]
-
-
-
-  Using --retry-failed
-
-  cm:bulk-publish:revert --retry-failed [LOG FILE NAME]
-```
-
-_See code: [@contentstack/cli-cm-bulk-publish](https://github.com/contentstack/cli/blob/main/packages/contentstack-bulk-publish/src/commands/cm/stacks/publish-revert.js)_
-
-## `csdx cm:stacks:seed [--repo <value>] [--org <value>] [-k <value>] [-n <value>] [-y <value>] [-s <value>] [--locale <value>]`
+## `csdx cm:stacks:seed [--repo <value>] [--org <value>] [--stack-api-key <value>] [--stack-name <value>] [-y] [--alias <value>] [--locale <value>]`
 
 Create a stack from existing content types, entries, assets, etc
 
 ```
 USAGE
-  $ csdx cm:stacks:seed [--repo <value>] [--org <value>] [-k <value>] [-n <value>] [-y <value>] [-s <value>]
-    [--locale <value>]
+  $ csdx cm:stacks:seed [--repo <value>] [--org <value>] [--stack-api-key <value>] [--stack-name <value>] [-y]
+    [--alias <value>] [--locale <value>]
 
 FLAGS
   -a, --alias=<value>          Alias of the management token
   -k, --stack-api-key=<value>  Provide stack API key to seed content to
   -n, --stack-name=<value>     Name of a new stack that needs to be created.
-  -o, --org=<value>            Provide Organization UID to create a new stack
-  -r, --repo=<value>           GitHub organization name or GitHub user name/repository name.
-  -s, --stack=<value>          Provide the stack UID to seed content.
-  -y, --yes=<value>            [Optional] Skip the stack confirmation.
+  -y, --yes                    [Optional] Skip the stack confirmation.
+      --org=<value>            Provide Organization UID to create a new stack
+      --repo=<value>           GitHub organization name or GitHub user name/repository name.
 
 DESCRIPTION
   Create a stack from existing content types, entries, assets, etc
@@ -3260,25 +1483,24 @@ Set region for CLI
 ```
 USAGE
   $ csdx config:set:region [REGION] [--cda <value> --cma <value> --ui-host <value> -n <value>] [--developer-hub
-    <value>] [--personalize <value>] [--launch <value>] [--studio <value>] [--asset-management <value>]
+    <value>] [--personalize <value>] [--launch <value>] [--studio <value>] [--cs-assets <value>]
 
 ARGUMENTS
   [REGION]  Name for the region
 
 FLAGS
-  -n, --name=<value>              Name for the region, if this flag is added then cda, cma and ui-host flags are
-                                  required
-      --asset-management=<value>  Custom host to set for Asset Management API
-      --cda=<value>               Custom host to set for content delivery API, if this flag is added then cma, ui-host
-                                  and name flags are required
-      --cma=<value>               Custom host to set for content management API, , if this flag is added then cda,
-                                  ui-host and name flags are required
-      --developer-hub=<value>     Custom host to set for Developer hub API
-      --launch=<value>            Custom host to set for Launch API
-      --personalize=<value>       Custom host to set for Personalize API
-      --studio=<value>            Custom host to set for Studio API
-      --ui-host=<value>           Custom UI host to set for CLI, if this flag is added then cda, cma and name flags are
-                                  required
+  -n, --name=<value>           Name for the region, if this flag is added then cda, cma and ui-host flags are required
+      --cda=<value>            Custom host to set for content delivery API, if this flag is added then cma, ui-host and
+                               name flags are required
+      --cma=<value>            Custom host to set for content management API, , if this flag is added then cda, ui-host
+                               and name flags are required
+      --cs-assets=<value>      Custom host to set for Contentstack Assets API
+      --developer-hub=<value>  Custom host to set for Developer hub API
+      --launch=<value>         Custom host to set for Launch API
+      --personalize=<value>    Custom host to set for Personalize API
+      --studio=<value>         Custom host to set for Studio API
+      --ui-host=<value>        Custom UI host to set for CLI, if this flag is added then cda, cma and name flags are
+                               required
 
 DESCRIPTION
   Set region for CLI
@@ -3310,7 +1532,7 @@ EXAMPLES
 
   $ csdx config:set:region --cma <custom_cma_host_url> --cda <custom_cda_host_url> --ui-host <custom_ui_host_url> --name "India" --studio <custom_studio_url>
 
-  $ csdx config:set:region --cma <custom_cma_host_url> --cda <custom_cda_host_url> --ui-host <custom_ui_host_url> --name "India" --asset-management <asset_management_url>
+  $ csdx config:set:region --cma <custom_cma_host_url> --cda <custom_cda_host_url> --ui-host <custom_ui_host_url> --name "India" --cs-assets <cs_assets_url>
 
   $ csdx config:set:region --cda <custom_cda_host_url> --cma <custom_cma_host_url> --ui-host <custom_ui_host_url> --name "India" --developer-hub <custom_developer_hub_url> --launch <custom_launch_url> --personalize <custom_personalize_url> --studio <custom_studio_url>
 ```
@@ -3335,7 +1557,7 @@ DESCRIPTION
   Display help for csdx.
 ```
 
-_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/6.2.40/src/commands/help.ts)_
+_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/6.2.48/src/commands/help.ts)_
 
 ## `csdx launch`
 
@@ -3655,7 +1877,7 @@ EXAMPLES
   $ csdx plugins
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.55/src/commands/plugins/index.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.67/src/commands/plugins/index.ts)_
 
 ## `csdx plugins:add PLUGIN`
 
@@ -3729,7 +1951,7 @@ EXAMPLES
   $ csdx plugins:inspect myplugin
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.55/src/commands/plugins/inspect.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.67/src/commands/plugins/inspect.ts)_
 
 ## `csdx plugins:install PLUGIN`
 
@@ -3778,7 +2000,7 @@ EXAMPLES
     $ csdx plugins:install someuser/someplugin
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.55/src/commands/plugins/install.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.67/src/commands/plugins/install.ts)_
 
 ## `csdx plugins:link PATH`
 
@@ -3809,7 +2031,7 @@ EXAMPLES
   $ csdx plugins:link myplugin
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.55/src/commands/plugins/link.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.67/src/commands/plugins/link.ts)_
 
 ## `csdx plugins:remove [PLUGIN]`
 
@@ -3850,7 +2072,7 @@ FLAGS
   --reinstall  Reinstall all plugins after uninstalling.
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.55/src/commands/plugins/reset.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.67/src/commands/plugins/reset.ts)_
 
 ## `csdx plugins:uninstall [PLUGIN]`
 
@@ -3878,7 +2100,7 @@ EXAMPLES
   $ csdx plugins:uninstall myplugin
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.55/src/commands/plugins/uninstall.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.67/src/commands/plugins/uninstall.ts)_
 
 ## `csdx plugins:unlink [PLUGIN]`
 
@@ -3922,7 +2144,7 @@ DESCRIPTION
   Update installed plugins.
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.55/src/commands/plugins/update.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/5.4.67/src/commands/plugins/update.ts)_
 
 ## `csdx tokens`
 
diff --git a/packages/contentstack/package.json b/packages/contentstack/package.json
index afb77514a9..d7b4d2e2a3 100755
--- a/packages/contentstack/package.json
+++ b/packages/contentstack/package.json
@@ -19,11 +19,12 @@
     "prepack": "pnpm compile && oclif manifest && oclif readme"
   },
   "dependencies": {
+    "@contentstack/apps-cli": "~2.0.0-beta.0",
     "@contentstack/cli-audit": "~2.0.0-beta.12",
     "@contentstack/cli-cm-export": "~2.0.0-beta.17",
     "@contentstack/cli-cm-import": "~2.0.0-beta.17",
     "@contentstack/cli-auth": "~2.0.0-beta.12",
-    "@contentstack/cli-bulk-operations": "^1.0.1",
+    "@contentstack/cli-bulk-operations": "~2.0.0-beta.0",
     "@contentstack/cli-cm-bootstrap": "~2.0.0-beta.17",
     "@contentstack/cli-cm-branches": "~2.0.0-beta.7",
     "@contentstack/cli-cm-clone": "~2.0.0-beta.18",
@@ -33,6 +34,7 @@
     "@contentstack/cli-command": "~2.0.0-beta.7",
     "@contentstack/cli-config": "~2.0.0-beta.9",
     "@contentstack/cli-launch": "^1.9.9",
+    "@contentstack/cli-cm-migrate-rte": "~2.0.0-beta.7",
     "@contentstack/cli-migration": "~2.0.0-beta.12",
     "@contentstack/cli-utilities": "~2.0.0-beta.8",
     "@contentstack/cli-variants": "~2.0.0-beta.13",
@@ -126,6 +128,9 @@
       "cm:stacks": {
         "description": "Stacks related operations"
       },
+      "app": {
+        "description": "Perform developer-hub app related activities"
+      },
       "launch": {
         "description": "Launch related operations"
       },
@@ -148,11 +153,13 @@
       "@contentstack/cli-cm-export-to-csv",
       "@contentstack/cli-cm-clone",
       "@contentstack/cli-migration",
+      "@contentstack/cli-cm-migrate-rte",
       "@contentstack/cli-cm-branches",
       "@contentstack/cli-audit",
       "@contentstack/cli-cm-import-setup",
       "@contentstack/cli-launch",
-      "@contentstack/cli-bulk-operations"
+      "@contentstack/cli-bulk-operations",
+      "@contentstack/apps-cli"
     ],
     "hooks": {
       "prerun": [