chore(release): bump version to 1.2.0[skip ci]

# [1.2.0](1.1.2...1.2.0) (2022-10-24)

### Features

* add verbose argument ([069d089](069d089))
* upgrade nitro version ([b30296c](b30296c))

CHANGELOG.md

@@ -1,3 +1,11 @@
+# [1.2.0](https://github.com/nitro-build/bitrise-step-nitro-ios/compare/1.1.2...1.2.0) (2022-10-24)
+
+
+### Features
+
+* add verbose argument ([069d089](https://github.com/nitro-build/bitrise-step-nitro-ios/commit/069d089d7b257bb103e4330ec5ee5055ecbca7db))
+* upgrade nitro version ([b30296c](https://github.com/nitro-build/bitrise-step-nitro-ios/commit/b30296cd136275753d9aaa333b97194d4e973a7f))
+
 ## [1.1.2](https://github.com/nitro-build/bitrise-step-nitro-ios/compare/1.1.1...1.1.2) (2022-10-13)
 
 

README.md

@@ -49,7 +49,7 @@ You can also run this step directly with [Bitrise CLI](https://github.com/bitris
 | `post_build_command` | Run command once build successfully finished (e.g. `yarn publish`) |  |  |
 | `output_directory` | The path to the directory where to place all of Nitro's output files |  | `$BITRISE_DEPLOY_DIR` |
 | `entry_file` | The entry file for bundle generation |  | `$ENTRY_FILE` |
-| `debug` | Enable verbose logs |  | `$NITRO_DEBUG_MODE` |
+| `verbose` | Enable verbose logs |  |  |
 | `fail_safe` | Runing the app in this mode allows you to prevent the build to fail but you can check the status in further steps |  | `$NITRO_FAIL_SAFE` |
 </details>
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "bitrise-step-nitro-ios",
-  "version": "1.1.2",
+  "version": "1.2.0",
   "repository": "git@github.com:nitro-build/bitrise-step-nitro-ios.git",
   "author": "Juan Pablo Garcia <juanpablogarcia@gmail.com>",
   "license": "MIT",