Skip to content

Commit 6e47427

Browse files
FishbowlerFishbowler
committed
Version 2.0.1
1 parent d283be3 commit 6e47427

File tree

1 file changed

+19
-19
lines changed

1 file changed

+19
-19
lines changed

‎README.md‎

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ Run your Flows on [Maestro Cloud](https://app.maestro.dev).
77
Add the following to your workflow. Note that you can use the `v1` tag if you want to keep using the latest version of the action, which will automatically resolve to all `v1.minor.patch` versions as they get published.
88

99
```yaml
10-
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.0
10+
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.1
1111
with:
1212
api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
1313
project-id: 'proj_01example0example1example2' # replace this with your actual project id
@@ -70,7 +70,7 @@ For more information on triggering workflows, check out [GitHub's documentation]
7070
## Android
7171

7272
```yaml
73-
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.0
73+
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.1
7474
with:
7575
api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
7676
project-id: 'proj_01example0example1example2'
@@ -84,7 +84,7 @@ For more information on triggering workflows, check out [GitHub's documentation]
8484
Include the ProGuard mapping file to deobfuscate Android performance traces:
8585

8686
```yaml
87-
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.0
87+
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.1
8888
with:
8989
api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
9090
project-id: 'proj_01example0example1example2'
@@ -95,7 +95,7 @@ Include the ProGuard mapping file to deobfuscate Android performance traces:
9595
## iOS
9696

9797
```yaml
98-
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.0
98+
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.1
9999
with:
100100
api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
101101
project-id: 'proj_01example0example1example2'
@@ -108,7 +108,7 @@ Include the ProGuard mapping file to deobfuscate Android performance traces:
108108
### .dSYM file
109109

110110
```yaml
111-
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.0
111+
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.1
112112
with:
113113
api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
114114
project-id: 'proj_01example0example1example2'
@@ -123,7 +123,7 @@ Include the ProGuard mapping file to deobfuscate Android performance traces:
123123
By default, the action is looking for a `.maestro` folder with Maestro flows in the root directory of the project. If you would like to customize this behaviour, you can override it with a `workspace` argument:
124124

125125
```yaml
126-
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.0
126+
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.1
127127
with:
128128
api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
129129
project-id: 'proj_01example0example1example2'
@@ -142,7 +142,7 @@ A name will automatically be provided according to the following order:
142142
If you want to override this behaviour and specify your own name, you can do so by setting the `name` argument:
143143

144144
```yaml
145-
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.0
145+
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.1
146146
with:
147147
api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
148148
project-id: 'proj_01example0example1example2'
@@ -182,7 +182,7 @@ jobs:
182182
HEAD_REF=$(gh pr view "$PR_NUMBER" --json headRefName --jq '.headRefName')
183183
echo "branch=$HEAD_REF" >> $GITHUB_OUTPUT
184184
185-
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.0
185+
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.1
186186
with:
187187
api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
188188
project-id: 'proj_01example0example1example2'
@@ -195,7 +195,7 @@ jobs:
195195
If you don't want the action to wait until the Upload has been completed as is the default behaviour, set the `async` argument to `true`:
196196

197197
```yaml
198-
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.0
198+
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.1
199199
with:
200200
api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
201201
project-id: 'proj_01example0example1example2'
@@ -206,7 +206,7 @@ If you don't want the action to wait until the Upload has been completed as is t
206206
Alternatively, you might want to still wait for the action but would like to configure the timeout period, set `timeout` argument to a number of minutes:
207207

208208
```yaml
209-
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.0
209+
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.1
210210
with:
211211
api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
212212
project-id: 'proj_01example0example1example2'
@@ -219,7 +219,7 @@ Alternatively, you might want to still wait for the action but would like to con
219219
If you want to pass environment variables along with your upload, add a multiline `env` argument:
220220

221221
```yaml
222-
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.0
222+
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.1
223223
with:
224224
api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
225225
project-id: 'proj_01example0example1example2'
@@ -236,7 +236,7 @@ You can use Maestro [Tags](https://maestro.mobile.dev/cli/tags) to filter which
236236
You can either pass a single value, or comma-separated (`,`) values.
237237

238238
```yaml
239-
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.0
239+
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.1
240240
with:
241241
api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
242242
project-id: 'proj_01example0example1example2'
@@ -252,7 +252,7 @@ You can specify which Android API level to use when running using the `android-a
252252
On Maestro Cloud, the default API level is 33 (Android 13). [Refer to Maestro Cloud docs](https://docs.maestro.dev/cloud/reference/configuring-os-version) for available Android emulator API levels.
253253

254254
```yaml
255-
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.0
255+
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.1
256256
with:
257257
api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
258258
project-id: 'proj_01example0example1example2'
@@ -267,7 +267,7 @@ You can specify which iOS Version to use when running in Maestro Cloud using the
267267
On Maestro Cloud, the default iOS version is 16. [Refer to Maestro Cloud docs](https://docs.maestro.dev/cloud/reference/configuring-os-version) for available iOS simulator versions. On Maestro Cloud, the default iOS version is 16.
268268

269269
```yaml
270-
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.0
270+
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.1
271271
with:
272272
api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
273273
project-id: 'proj_01example0example1example2'
@@ -282,7 +282,7 @@ If your workspace contains Web tests that are supposed to run on a real browser,
282282
You don't have to specify `app-file`.
283283

284284
```yaml
285-
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.0
285+
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.1
286286
with:
287287
api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
288288
project-id: 'proj_01example0example1example2'
@@ -295,13 +295,13 @@ You can use an already uploaded binary in Maestro Cloud using the `app-binary-id
295295

296296
```yaml
297297
- id: upload
298-
uses: mobile-dev-inc/action-maestro-cloud@v2.0.0
298+
uses: mobile-dev-inc/action-maestro-cloud@v2.0.1
299299
with:
300300
api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
301301
project-id: 'proj_01example0example1example2'
302302
app-file: app.zip
303303
304-
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.0
304+
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.1
305305
with:
306306
api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
307307
project-id: 'proj_01example0example1example2'
@@ -313,7 +313,7 @@ You can use an already uploaded binary in Maestro Cloud using the `app-binary-id
313313
To switch the device locale on a remote device from a default one (en_US) `device-locale` parameter should be used. The value is a combination of lowercase ISO-639-1 code and uppercase ISO-3166-1 code, i.e. "de_DE" for Germany.
314314

315315
```yaml
316-
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.0
316+
- uses: mobile-dev-inc/action-maestro-cloud@v2.0.1
317317
with:
318318
api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
319319
project-id: 'proj_01example0example1example2'
@@ -334,7 +334,7 @@ In order to access these variables you can use the following approach:
334334

335335
```yaml
336336
- id: upload
337-
uses: mobile-dev-inc/action-maestro-cloud@v2.0.0
337+
uses: mobile-dev-inc/action-maestro-cloud@v2.0.1
338338
with:
339339
api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }}
340340
project-id: 'proj_01example0example1example2'

0 commit comments

Comments
 (0)