3.0.0

Breaking changes:

The --no-daemon Gradle flag is no longer set by default. When a workflow runs multiple Gradle commands, this results in faster subsequent Gradle executions as the existing Gradle daemon is reused (instead of stopping, then starting a new one). This shouldn't cause issues, but if it does, you can revert to the previous behavior by setting gradle_options to --stacktrace --no-daemon.

The following deprecated inputs have been removed:

• apk_file_include_filter (use app_file_include_filter instead)
• apk_file_exclude_filter (use app_file_exclude_filter instead)

What's Changed

• Generate readme by @mateherber in #91
• Test running on JDK 11 by @ofalvai in #92
• Use custom bot token in stale workflow by @bitrise-coresteps-bot in #93
• Configure Renovate by @renovate in #94
• Apply YAML lint by @ofalvai in #95
• Delete leftover docker-compose.yml by @ofalvai in #97
• [BE-46] Make sure jenv finds at least one valid JAVA installation by @fehersanyi-bitrise in #99
• removed a deprecated link from step.yml by @daniCsorba in #100
• Metrics collection by @ofalvai in #102
• Fix optional --build-file flag in metrics by @ofalvai in #103
• Load plugin from Maven Central by @ofalvai in #104
• Update module github.com/hashicorp/go-retryablehttp to v0.7.7 [SECURITY] by @renovate in #106
• Remove --no-daemon from default flags by @ofalvai in #107
• Remove deprecated filter inputs by @ofalvai in #108
• Remove unreleased metrics collection option by @ofalvai in #109

Full Changelog: 2.0.1...3.0.0