# OpenZeppelin CLI 2.8: Opt out of Upgradeability

**URL:** <https://forum.openzeppelin.com/t/openzeppelin-cli-2-8-opt-out-of-upgradeability/2477>\
**Category:** Announcements\
**Created:** [March 25, 2020, 4:09pm UTC](https://forum.openzeppelin.com/t/openzeppelin-cli-2-8-opt-out-of-upgradeability/2477 "2020-03-25T16:09:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![frangio](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/frangio/32/15251_2.png) [@frangio](https://forum.openzeppelin.com/u/frangio)\
**Post date:** [March 25, 2020, 4:09pm UTC](https://forum.openzeppelin.com/t/openzeppelin-cli-2-8-opt-out-of-upgradeability/2477/1 "2020-03-25T16:09:12Z")

</div>

![image](https://us1.discourse-cdn.com/flex022/uploads/zeppelin/original/2X/8/8a978df74645cf714d524abc5dd0c61148b1f2fc.png)

With this new release you’ll be able to **deploy non-upgradeable instances** of your contracts. We hope you like it! Read on to find out more.

```nohighlight
npm install @openzeppelin/cli

```

* * *

## Opt out of Upgradeability

Until today, using the CLI you’d only be able to deploy upgradeable contracts. This developed from our initial goal of building an encompassing upgradeability solution. Over time, we realized that the CLI could be much more useful and added more general features like `send-tx` and `call`. Coupled with the interactive interface users have found these commands an essential part of their toolbox. The one thing missing was the ability to deploy non-upgradeable contract instances.

**The CLI 2.8 ships with a brand new subcommand called `deploy`.** It is the “one-stop shop” for deploying contracts. Using this command you will be able to deploy upgradeable and minimal proxy instances, like the current `create` command, and non-upgradeable instances, which we are calling _regular_, all under a unified interface.

 ![demo](https://us1.discourse-cdn.com/flex022/uploads/zeppelin/original/2X/8/8070e99025e892cb198475d4028b4f28feda3728.gif)

* * *

_The `deploy` command is our first step towards reducing the friction around using upgradeability. If you want to know more, check out our [Q1 roadmap](https://github.com/OpenZeppelin/openzeppelin-sdk/issues/1424) and the [SDK 3.0 design document](https://forum.openzeppelin.com/t/sdk-3-0-design-document/2251)._

---

<div class="post-metadata">

**Author:** ![abcoathup](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/abcoathup/32/415_2.png) [@abcoathup](https://forum.openzeppelin.com/u/abcoathup)\
**Post date:** [March 30, 2020, 2:42am UTC](https://forum.openzeppelin.com/t/openzeppelin-cli-2-8-opt-out-of-upgradeability/2477/2 "2020-03-30T02:42:20Z")

</div>

I am biased, but I ❤ regular deploys.

---

<div class="post-metadata">

**Author:** ![abcoathup](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/abcoathup/32/415_2.png) [@abcoathup](https://forum.openzeppelin.com/u/abcoathup)\
**Post date:** [July 29, 2020, 4:11am UTC](https://forum.openzeppelin.com/t/openzeppelin-cli-2-8-opt-out-of-upgradeability/2477/3 "2020-07-29T04:11:46Z")

</div>

Split this topic on July 29, 2020, 4:11am UTC

A post was split to a new topic: [Differences between t3 deploy options](https://forum.openzeppelin.com/t/differences-between-t3-deploy-options/3426)