Repository navigation
fix(ci): install the Android SDK with setup-android v4 - #72
Merged
Merged
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.
Summary
android-actions/setup-androidfromv3tov4in thekotlinjob.mainand on every open PR —and none of them failed for a reason in this repository. The
v3default forthe action's
packagesinput is'tools platform-tools', and Google stoppedserving the deprecated
toolspackage around 2026-09-15, sosdkmanagerexits1 with
Failed to find package 'tools'before a line of Kotlin is compiled.v4droppedtoolsfrom the default and skips it with a warning when askedfor it explicitly, which makes this a drop-in bump: the only thing that stops
being installed is a package that no longer exists.
Validation
pnpm lintpnpm typecheckpnpm testpnpm build— plusbuild:site,codegen:native:check,typecheck:strict-templates,check:themeandtest:e2e(11/11)cd packages/egui && cargo fmt --check && cargo clippy --all-targets -D warnings && cargo test --allcd packages/compose && ./gradlew clean buildagainst a real Android SDK —BUILD SUCCESSFUL, 98 tasks, no warnings. The port itself was never broken.
Notes
vitest3.2.7 → 4.1.11) stays red after this lands, for an unrelatedreason: it bumps
vitestalone and leaves@vitest/coverage-v8(root) and@vitest/browser(apps/docs) on^3.2.7. The suite runs, then the v8coverage provider dies with
Cannot read properties of undefined (reading 'fetchCache'). The three move together or not at all..github/dependabot.ymlignores every major forgithub-actions("Major upgrades reviewed manually"), which is why
v4was never proposed.The rule is deliberate; what is missing is the periodic manual review.