@appzung/cli/CHANGELOG.md

AppZung CLI

# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [1.13.2] - 2026-02-23

### Modified

- Add dry-run flag to deploy commands

## [1.13.1] - 2026-01-23

### Modified

- Bundling will now match behavior of react-native-xcode.sh

## [1.13.0] - 2026-01-13

### Added

- Added support for React Native 0.83 with Hermes

## [1.12.0] - 2025-12-22

### Added

- Added --json flag support for releases:list command
- Added --api-key flag support for releases:list command
- Added --limit flag support for releases:list command

## [1.11.0] - 2025-08-15

### Added

- Added --json flag support for deployment commands

## [1.10.0] - 2025-06-15

### Added

- Added basic "appzung releases deploy-expo" command for simplifying releasing updates for Expo projects

## [1.9.0] - 2025-06-15

### Added

- Improved workflow in interactive mode when creating a project/application
- Better formatting/sorting of options for application platform, project framework and project release type

## [1.8.0] - 2025-05-30

### Added

- If you rely on your project's package.json version for your native binary version, you may use `--use-package-json-version` instead of `--target-binary-version` or auto-detection from native files.

## [1.7.1] - 2025-05-15

### Modified

- When migrating with `appzung codepush migrate`, your deployments won't be automatically migrated to release channels anymore as AppCenter removed the API (as part of AppCenter gradual shutdown)

## [1.7.0] - 2025-04-23

### Added

- When deploying, use `--private-key` instead of `--private-key-file` to specify a file path or directly the private key content
- The `billing active-users-history` command lets you see your current and past billing MAU

## [1.6.0] - 2025-04-12

### Added

- While it's recommended to use project API keys for security, you may now create organization API keys that have access to every releases in the organization

## [1.5.0] - 2025-03-24

### Added

- Use the --react-native-cli-path flag to handle particular monorepo setups when needed

## [1.4.0] - 2025-03-19

### Added

- Use the --sentry-sourcemap-debug-id flag to make it easier sending sourcemaps to Sentry

## [1.3.0] - 2025-03-02

### Added

- Basic metrics in `releases show`
- Edit projects, applications, and release channels

## [1.2.0] - 2025-02-18

### Added

- Restrict API keys to allowed IP ranges