scan-with-appsweep 3.0.1

[pascalj]

What to do if the build fails?

At the moment contributors do not have access to the CI workflow triggered by StepLib PRs. In case of a failed build, we ask for your patience. Maintainers of Bitrise Steplib will sort it out for you or inform you if any further action is needed.

New Pull Request Checklist

Please mark the points which you did / accept.

• I will not move an already shared step version's tag to another commit
• I read the Step Development Guideline
• I have a test for my Step, which can be run with bitrise run test (in the step's repository)
• I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
• I read and accept the Abandoned Step policy

[bitrise-coresteps-bot]

Don't forget to follow semantic versioning! Breaking changes (including step inputs) should be in major versions only.

step.yml changes compared to previous version:

--- steps/scan-with-appsweep/3.0.0/step.yml	2025-03-13 09:07:59
+++ steps/scan-with-appsweep/3.0.1/step.yml	2025-03-13 09:07:59
@@ -10,8 +10,8 @@
 source_code_url: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep
 support_url: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep/issues
-published_at: 2025-02-04T08:40:54.61564+01:00
+published_at: 2025-03-07T11:53:23.652163+01:00
 source:
   git: https://github.com/Guardsquare/bitrise-step-scan-with-appsweep.git
-  commit: c7e0e6f16b8876d05ddfb0680b1041cab5f3dcb2
+  commit: af6daeb73c79e4cae73966a9f3b6e9c0a0fcf8e7
 host_os_tags:
 - osx-10.10
@@ -40,4 +40,5 @@
     is_required: true
     is_sensitive: true
+    summary: The AppSweep API key to use for the scan.
     title: AppSweep API key
 - commit_hash: ccd4e70c9dde1f309691af54aa43590c2f0efc7d
@@ -45,4 +46,5 @@
     description: |
       The commit for this build. This commit will be associated with the app scan.
+    summary: The commit hash to show in AppSweep for the scan.
     title: Git commit hash
 - ios_archive_path: 
@@ -52,4 +54,5 @@
       AppSweep works with both, an IPA file or an xcarchive directory. This has to be set if you want to analyze iOS builds.
     is_required: false
+    summary: The iOS app (IPA or xcarchive file) to scan.
     title: The path of the iOS archive
 - ios_dsyms_dir_path: 
@@ -59,10 +62,13 @@
       Should the archive not include debug symbols, it is possible to pass in the path to the dSYM directory explicitly. Lacking debug symbols prevents AppSweep from performing an in-depth analysis.
     is_required: false
+    summary: The path to the directory of additional dSYM files to use.
     title: The path of the dSYM directory.
 - android_app_path: 
   opts:
+    category: Android
     description: |
       Path name to the built app. Can be an Android apk / aab.
     is_required: false
+    summary: The Android app (apk or aab file) to scan.
     title: The path of the Android app
 - android_mappingfile_path: null
@@ -72,4 +78,5 @@
       Path to the obfuscation mapping file. E.g., ./app/build/outputs/mapping/debug/mapping.txt
     is_required: false
+    summary: The path to the obfuscation mapping file.
     title: The path to the obfuscation mapping file
 - android_project_location: 
@@ -79,4 +86,5 @@
       Set this to the location of your project inside your repository. Inside this directory, the build file should be `./app/build.gradle` and `gradlew` should be directly in the `project_location`.
     is_required: false
+    summary: The file path to your project inside your repository.
     title: Project file path
 outputs: