apk-info 1.4.7

[SumeraMartin]

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

[CLAassistant]

All committers have signed the CLA.

[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/apk-info/1.4.6/step.yml	2025-12-01 17:27:14
+++ steps/apk-info/1.4.7/step.yml	2025-12-01 17:27:15
@@ -6,8 +6,8 @@
 source_code_url: https://github.com/thefuntasty/bitrise-step-apk-info
 support_url: https://github.com/thefuntasty/bitrise-step-apk-info/issues
-published_at: 2021-06-02T20:24:31.688097+02:00
+published_at: 2025-12-01T11:27:03.389818+01:00
 source:
   git: https://github.com/futuredapp/bitrise-step-apk-info.git
-  commit: 2897c74e1af045467695842ff1d84622848d9079
+  commit: fab654713ec1327dc68106bbf023a35e1f01ebd3
 project_type_tags:
 - android