Repository navigation
Update dependency rules_android to v0.8.0 - #153
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.7.3→0.8.0Release Notes
bazelbuild/rules_android (rules_android)
v0.8.0Release summary
We’ve cleaned up legacy Android flags in native Bazel and ported them to rules_android. These changes will take effect in rules_android 0.8.0+ and Bazel 10+.
Android Configuration Flag Starlarkification
We’ve refactored the rule implementations to no longer read from the Bazel Android configuration fragment and instead obtain that information directly from new Starlark flags in rules_android. We’ve added flag_alias()es to rules_android’s MODULE file such that existing uses of relevant Android configuration flags will still work seamlessly.
Android Execution Strategy Flags
The legacy Bazel flags to control Android build execution strategy could not be Starlarkified, and their respective behaviors instead are expressed in the form of many
--modify_execution_info flagsin android_persistent_workers.bazelrc. We encourage you to copy this file into your project to avoid having to manually specify a large number of execution info flags.If you relied on e.g.
--persistent_android_dex_desugar before, you can activate that behavior with the equivalent--config=persistent_android_dex_desugarafter importing the worker bazelrc.Deprecated Flags
We deprecated around 30 obsolete or no-op native Android flags from Bazel. These should be removed from bazelrc files, scripts, and build invocations in general.
Usage
Using Bzlmod with Bazel 6 or greater
common --enable_bzlmodin.bazelrc.MODULE.bazelfile:Using WORKSPACE
Paste this snippet into your
WORKSPACE.bazelfile:In BUILD
Load the rules from
rules_android:Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.