# release-cli

> Publish a new version of your app

Latest version **0.3.0** (published 2017-12-27) · MPL-2.0 license · 0 weekly downloads

## Install

```sh
npm install release-cli
pnpm add release-cli
yarn add release-cli
bun add release-cli
```

Provides the command `release`.

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support; pre 1.0.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 0.3.0 |
| Published | 2017-12-27 |
| First published | 2016-05-01 |
| Weekly downloads | 0 |
| License | MPL-2.0 |
| TypeScript types | none |
| Module format | CommonJS |
| Node | >=8 |
| Dependencies | 6 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 0 |
| Author | Seth Holladay |
| Maintainers | sholladay |
| Keywords | cli-app, cli, bin, continuous, devops, deploy, release, publish, process, automate, automation, bump, version |

## Links

- npm: https://www.npmjs.com/package/release-cli
- Repository: https://github.com/sholladay/release-cli
- Issues: https://github.com/sholladay/release-cli/issues
- npm.io page: https://npm.io/package/release-cli

## Dependencies (6)

- [ora](https://npm.io/package/ora.md) ^1.3.0
- [meow](https://npm.io/package/meow.md) ^4.0.0
- [chalk](https://npm.io/package/chalk.md) ^2.1.0
- [fresh-cli](https://npm.io/package/fresh-cli.md) ^1.1.1
- [branch-name](https://npm.io/package/branch-name.md) ^1.0.0
- [update-notifier](https://npm.io/package/update-notifier.md) ^2.2.0

## Alternatives

- [@salesforce/cli](https://npm.io/package/@salesforce/cli.md) — 389.7K weekly downloads
- [@mintlify/cli](https://npm.io/package/@mintlify/cli.md) — 208.9K weekly downloads
- [@grafana/e2e-selectors](https://npm.io/package/@grafana/e2e-selectors.md) — 128.7K weekly downloads
- [mintlify](https://npm.io/package/mintlify.md) — 112.0K weekly downloads
- [@intlayer/cli](https://npm.io/package/@intlayer/cli.md) — 22.8K weekly downloads

## Recent versions

- 0.3.0 (latest) — 2017-12-27
- 0.2.5 — 2016-08-10
- 0.2.4 — 2016-08-10
- 0.2.3 — 2016-08-07
- 0.2.2 — 2016-08-02
- 0.2.1 — 2016-06-12
- 0.2.0 — 2016-06-12
- 0.1.1 — 2016-06-01
- 0.1.0 — 2016-05-30
- 0.0.2 — 2016-05-03
- 0.0.1 — 2016-05-01

## README

# release-cli [![Build status for Release CLI](https://img.shields.io/circleci/project/sholladay/release-cli/master.svg "Build Status")](https://circleci.com/gh/sholladay/release-cli "Builds")

> Publish a new version of your app

## Why?

 - Automate your release process.
 - Don't repeat yourself.
 - One step closer to continuous delivery.
 - Predictable, easy to use process.

## Install

```sh
npm install release-cli --global
```

## Usage

```
$ release --help

  Usage
    $ release [patch | minor | major]

  Example
    $ release patch
    ⇑ 0.0.1
    $ release minor
    ⇑ 0.1.0
    $ release major
    ⇑ 1.0.0
```

Perform a release, incrementing the [version](http://semver.org/).

```
$ release patch
⇑ 0.0.1
```

## Related

 - [delivr](https://github.com/sholladay/delivr) - Build your code and ship it to S3
 - [build-dir](https://github.com/sholladay/build-dir) - Get a place to put your build

## Contributing

See our [contributing guidelines](https://github.com/sholladay/release-cli/blob/master/CONTRIBUTING.md "Guidelines for participating in this project") for more details.

1. [Fork it](https://github.com/sholladay/release-cli/fork).
2. Make a feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. [Submit a pull request](https://github.com/sholladay/release-cli/compare "Submit code to this project for review").

## License

[MPL-2.0](https://github.com/sholladay/release-cli/blob/master/LICENSE "License for release-cli") © [Seth Holladay](https://seth-holladay.com "Author of release-cli")

Go make something, dang it.

---
_Source: https://npm.io/package/release-cli · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._