chore(release): bump version to 4.5.0-beta.1[skip ci]

# [4.5.0-beta.1](4.4.1...4.5.0-beta.1) (2023-01-28)

### Features

* upgrade nitro CLI version ([c180211](c180211))

CHANGELOG.md

@@ -1,3 +1,10 @@
+# [4.5.0-beta.1](https://github.com/nitro-build/bitrise-step-nitro-ios/compare/4.4.1...4.5.0-beta.1) (2023-01-28)
+
+
+### Features
+
+* upgrade nitro CLI version ([c180211](https://github.com/nitro-build/bitrise-step-nitro-ios/commit/c180211fd573d3ed5fdd29a20b47f33c46a3093c))
+
 ## [4.4.1](https://github.com/nitro-build/bitrise-step-nitro-ios/compare/4.4.0...4.4.1) (2023-01-10)
 
 

README.md

@@ -55,6 +55,7 @@ You can also run this step directly with [Bitrise CLI](https://github.com/bitris
 | `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` |
 | `verbose` | Enable verbose logs |  | `no` |
+| `debug` | Enable step debugging |  | `no` |
 | `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` |
 | `api_key` | The API key provided by Nitro. It should be defined by setting NITRO_API_KEY secret. | sensitive | `$NITRO_API_KEY` |
 </details>

package.json

@@ -1,6 +1,6 @@
 {
   "name": "bitrise-step-nitro-ios",
-  "version": "4.4.1",
+  "version": "4.5.0-beta.1",
   "repository": "[email protected]:nitro-build/bitrise-step-nitro-ios.git",
   "author": "Juan Pablo Garcia <[email protected]>",
   "license": "MIT",