diff --git a/README.md b/README.md index 3aac696..32a3710 100644 --- a/README.md +++ b/README.md @@ -7,7 +7,7 @@ Run your Flows on [Maestro Cloud](https://cloud.mobile.dev). 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. ```yaml -- uses: mobile-dev-inc/action-maestro-cloud@v1.4.0 +- uses: mobile-dev-inc/action-maestro-cloud@v1.4.1 with: api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }} app-file: @@ -45,7 +45,7 @@ jobs: # Android ```yaml -- uses: mobile-dev-inc/action-maestro-cloud@v1.4.0 +- uses: mobile-dev-inc/action-maestro-cloud@v1.4.1 with: api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }} app-file: app/build/outputs/apk/debug/app-debug.apk @@ -58,7 +58,7 @@ jobs: Include the Proguard mapping file to deobfuscate Android performance traces: ```yaml -- uses: mobile-dev-inc/action-maestro-cloud@v1.4.0 +- uses: mobile-dev-inc/action-maestro-cloud@v1.4.1 with: api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }} app-file: app/build/outputs/apk/release/app-release.apk @@ -68,7 +68,7 @@ Include the Proguard mapping file to deobfuscate Android performance traces: # iOS ```yaml -- uses: mobile-dev-inc/action-maestro-cloud@v1.4.0 +- uses: mobile-dev-inc/action-maestro-cloud@v1.4.1 with: api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }} app-file: .app @@ -80,7 +80,7 @@ Include the Proguard mapping file to deobfuscate Android performance traces: ### .dSYM file ```yaml -- uses: mobile-dev-inc/action-maestro-cloud@v1.4.0 +- uses: mobile-dev-inc/action-maestro-cloud@v1.4.1 with: api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }} app-file: .app @@ -94,7 +94,7 @@ Include the Proguard mapping file to deobfuscate Android performance traces: 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: ```yaml -- uses: mobile-dev-inc/action-maestro-cloud@v1.4.0 +- uses: mobile-dev-inc/action-maestro-cloud@v1.4.1 with: api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }} app-file: app.zip @@ -112,7 +112,7 @@ A name will automatically be provided according to the following order: If you want to override this behaviour and specify your own name, you can do so by setting the `name` argument: ```yaml -- uses: mobile-dev-inc/action-maestro-cloud@v1.4.0 +- uses: mobile-dev-inc/action-maestro-cloud@v1.4.1 with: api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }} app-file: app.zip @@ -124,7 +124,7 @@ If you want to override this behaviour and specify your own name, you can do so 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`: ```yaml -- uses: mobile-dev-inc/action-maestro-cloud@v1.4.0 +- uses: mobile-dev-inc/action-maestro-cloud@v1.4.1 with: api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }} app-file: app.zip @@ -136,7 +136,7 @@ If you don't want the action to wait until the Upload has been completed as is t If you want to pass environment variables along with your upload, add a multiline `env` argument: ```yaml -- uses: mobile-dev-inc/action-maestro-cloud@v1.4.0 +- uses: mobile-dev-inc/action-maestro-cloud@v1.4.1 with: api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }} app-file: app.zip @@ -152,7 +152,7 @@ You can use Maestro (Tags)[https://maestro.mobile.dev/cli/tags] to filter which You can either pass a single value, or comma-separated (`,`) values. ```yaml -- uses: mobile-dev-inc/action-maestro-cloud@v1.4.0 +- uses: mobile-dev-inc/action-maestro-cloud@v1.4.1 with: api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }} app-file: app.zip @@ -167,7 +167,7 @@ You can specify what Android API level to use when running in Maestro Cloud usin The default API level is 30. ```yaml -- uses: mobile-dev-inc/action-maestro-cloud@v1.4.0 +- uses: mobile-dev-inc/action-maestro-cloud@v1.4.1 with: api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }} app-file: app.apk @@ -181,7 +181,7 @@ You can specify what **major** iOS Version to use when running in Maestro Cloud The default iOS version is 15. ```yaml -- uses: mobile-dev-inc/action-maestro-cloud@v1.4.0 +- uses: mobile-dev-inc/action-maestro-cloud@v1.4.1 with: api-key: ${{ secrets.MAESTRO_CLOUD_API_KEY }} app-file: app.zip diff --git a/dist/index.js b/dist/index.js index 3a1d1c8..aa102fc 100644 --- a/dist/index.js +++ b/dist/index.js @@ -47036,7 +47036,7 @@ const run = () => __awaiter(void 0, void 0, void 0, function* () { env: env, agent: 'github', androidApiLevel: androidApiLevel, - iOSVersion, + iOSVersion: iOSVersion, includeTags: includeTags, excludeTags: excludeTags, }; @@ -47185,6 +47185,9 @@ function getInferredName() { function getAndroidApiLevel(apiLevel) { return apiLevel ? +apiLevel : undefined; } +function getIOSVersion(iosVersion) { + return iosVersion ? +iosVersion : undefined; +} function parseTags(tags) { if (tags === undefined || tags === '') return []; @@ -47208,7 +47211,7 @@ function getParameters() { const mappingFile = mappingFileInput && (0, app_file_1.validateMappingFile)(mappingFileInput); const async = core.getInput('async', { required: false }) === 'true'; const androidApiLevelString = core.getInput('android-api-level', { required: false }); - const iOSVersion = core.getInput('ios-version', { required: false }); + const iOSVersionString = core.getInput('ios-version', { required: false }); const includeTags = parseTags(core.getInput('include-tags', { required: false })); const excludeTags = parseTags(core.getInput('exclude-tags', { required: false })); var env = {}; @@ -47230,6 +47233,7 @@ function getParameters() { const repoName = getRepoName(); const pullRequestId = getPullRequestId(); const androidApiLevel = getAndroidApiLevel(androidApiLevelString); + const iOSVersion = getIOSVersion(iOSVersionString); return { apiUrl, name,