Electrode Native
v0.41
v0.41
  • Introduction
  • INTRODUCTION
    • Overview
      • What is Electrode Native
      • Why use Electrode Native
      • What is a MiniApp
      • Electrode Native workflow
      • Native dependencies management
      • JS/Native communication
      • Requirements
      • Upgrading Electrode Native
      • Contributing
  • REFERENCE
    • Bundle Store
    • Composite
    • Container
      • What's inside
      • Publication
      • Integration
      • Initialization
      • Launching MiniApps
    • Cauldron
      • Structure
      • Setup
      • Compatibility checks
      • Guidelines
    • Manifest
      • Override
      • Native Modules
      • Configurable Modules
    • Runner
    • APIs
      • Project Generation
      • Implementation
      • Versioning
      • Guidelines
    • Bridge
      • Message Types
      • Communication
      • Leveraging APIs
    • CLI
      • Global CLI
      • Local CLI
    • GLOSSARY
  • GUIDES
    • Debugging multiple MiniApps
  • CLI COMMANDS
    • add
    • bundlestore
      • create
      • delete
      • upload
      • use
    • binarystore
      • add
      • get
      • remove
    • code-push
      • patch
      • release
      • promote
    • compat-check
    • create-api-impl
    • create-api
    • create-composite
    • create-container
    • create-plugin-config
    • publish-container
    • transform-container
    • create-miniapp
    • link
    • regen-api
    • regen-api-impl
    • run-android
    • run-ios
    • start
    • unlink
    • upgrade-miniapp
    • cauldron add
      • file
      • jsapiimpls
      • miniapps
      • nativeapp
    • cauldron config
      • get
    • cauldron del
      • file
      • jsapiimpls
      • miniapps
      • nativeapp
    • cauldron get
      • config
      • dependency
      • nativeapp
    • cauldron repo
      • add
      • clear
      • current
      • list
      • remove
      • use
    • cauldron update
      • file
      • jsapiimpls
      • miniapps
      • nativeapp
    • cauldron batch
    • cauldron regen-container
    • cauldron upgrade
    • cauldron why
    • github
      • github create-ref
      • github delete-ref
      • github align-dependencies
    • platform
      • plugins
        • list
        • search
      • config
        • set
        • get
        • del
        • list
      • install
      • versions
      • uninstall
      • use
Powered by GitBook
On this page
  • Description
  • Syntax
  • Options
  • Related commands
  1. CLI COMMANDS
  2. code-push

promote

PreviousreleaseNextcompat-check

Last updated 4 years ago

code-push need to be met in order to run this command

Description

  • Promote a CodePush release to a different deployment name and/or native application versions.

Syntax

ern code-push promote

Options

--description/--des

  • Description of the changes made to the app with this release. If omitted, the description from the release being promoted will be used.

  • Default Empty string

--disableDuplicateReleaseError

  • When this flag is set, promoting a package that is identical to the latest release on the target deployment will produce a warning instead of an error

  • Default false

--force/-f

  • Bypass all compatibility checks and force OTA update through CodePush. USE AT YOUR OWN RISK

  • Default false

--label/-l

  • Promote the release matching this specific label.

  • Default The latest release matching sourceDescriptor/sourceDeploymentName pair will be promoted.

--mandatory/-m

  • Specify that the promoted release is mandatory (will be immediately downloaded and installed).

  • Default false

--reuseReleaseBinaryVersion

  • Indicates whether to reuse the target binary version that was used for the initial release

  • If omitted, and targetBinaryVersion is not set, the promotion will target the exact version of the descriptor

  • This option is mutually exclusive with targetBinaryVersion

--rollout/-r <percentage>

  • Specify the percentage of users who will have access to this release.

  • Default 100

--skipConfirmation/-s

  • Skip confirmation prompts

  • Default false

--skipNativeDependenciesVersionAlignedCheck/-n

  • Skip the check to compare native dependencies version alignment

  • This flag helps skipping native dependencies check for promoting same bundle label to multiple target versions

  • Default false

--sourceDeploymentName

  • The deployment name of the release to promote (Staging for example).

  • Default The command will prompt to input the deployment name, or display a list of deployment names stored in the Cauldron, to choose from.

--sourceDescriptor <descriptor>

  • Specify the native application version from which to promote a release in the form of a complete native application descriptor.

  • The release to be promoted will be the latest non disabled release of this native application version.

  • Default The command will list all released native applications versions stored in the Cauldron and will prompt to select a target native application version from the list.

--targetBinaryVersion/-t <targetBinaryVersion>

  • Semver expression that specifies the binary app version this promotion is targeting

  • If omitted, and reuseReleaseBinaryVersion is not set, the promotion will target the exact version of the descriptor

  • If versionModifier is specified in the codePush config, it will be applied

  • For using targetBinaryVersion option users must target only 1 descriptor

  • For using targetBinaryVersion option users cannot use semVerDescriptor

  • This option is mutually exclusive with reuseReleaseBinaryVersion

--targetDeploymentName

  • The deployment name to promote the release to (Production for example).

  • Default The command will prompt to input the deployment name, or display a list of deployment names stored in the Cauldron, to choose from.

--targetDescriptors <descriptors..>

  • Specify one or more target native application version to promote the release to, in the form of a complete native application descriptor list (separated by spaces).

  • The target descriptor can be the same as the source descriptor if the promotion is only changing the deployment name (for example promoting a release from Staging to Production for the same native application version).

--targetSemVerDescriptor <descriptor>

  • A native descriptor using a semantic version string for its version. The promotion will target all native application versions matching the semver.

  • If no targetDescriptors nor a targetSemVerDescriptor is specified, the command will list all released native application versions stored in the Cauldron and will display a prompt to select one or more target native application version(s) for the promotion.

Related commands

| Issue a CodePush release

| Patch a release

prerequisites
code-push release
code-push patch