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

patch

Previouscode-pushNextrelease

Last updated 4 years ago

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

Description

  • Patch a CodePush release.

  • This command only works for entries that have been released through ern code-push release or promoted through ern code-push promote.

  • Update the corresponding CodePush entry in Cauldron with the changes.

Syntax

ern code-push patch

Options

--descriptor/-d <descriptor>

  • Specify a target native application version (following the complete native application descriptor format) that contains the CodePush release to patch.

  • 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.

--label/-l

  • Specify the label (identifier) of the CodePush release to patch.

  • Default The command will display a prompt to input the label.

--disabled/-x

  • Update the distribution status of the matched CodePush release. Setting this flag to true will disable the CodePush release distribution, while setting this flag to false will enable the CodePush release distribution.

  • Default No change to the distribution status.

--deploymentName/-d <deploymentName>

  • Update the CodePush deployment name (Production, Staging ...) of the matched release.

  • Default No change to the deployment name.

--mandatory/-m

  • Update the mandatory status of the CodePush release entry. Setting this flag to true will make the CodePush release mandatory (it will be immediately downloaded and installed), whereas setting this flag to false will make the CodePush release non mandatory.

  • Default No change to the mandatory status.

--rollout/-r <percentage>

  • Update the percentage of users who will have access to the CodePush release.

  • Default No change to the rollout percentage.

--description/--des

  • Description of the changes made to the app with this release

  • Default Empty String

Related commands

| Promote a release to a different deployment name

| Issue a CodePush release

prerequisites
code-push promote
code-push release