Fast-follow on the Dockerfile fix. The next failure in the v2026.06.01 chain: android.yml release build (run 110, job 282) failed at lintVitalRelease:
AndroidManifest.xml:13: Error: Remove androidx.work.WorkManagerInitializer
from your AndroidManifest.xml when using on-demand initialization.
[RemoveWorkManagerInitializer from androidx.work]
MinstrelApplication implements Configuration.Provider and supplies HiltWorkerFactory, but the work-runtime library auto-registers WorkManagerInitializer via androidx-startup, racing the on-demand path. Lint catches this as a release blocker. AOSP-recommended fix: merge the InitializationProvider entry and remove the nested WorkManagerInitializer meta-data with tools:node="remove".
After merge I'll force-move v2026.06.01 to the new main HEAD; the workflow concurrency: cancel-in-progress will kill the in-flight tag runs from the broken HEAD.
Fast-follow on the Dockerfile fix. The next failure in the v2026.06.01 chain: `android.yml` release build (run 110, job 282) failed at `lintVitalRelease`:
```
AndroidManifest.xml:13: Error: Remove androidx.work.WorkManagerInitializer
from your AndroidManifest.xml when using on-demand initialization.
[RemoveWorkManagerInitializer from androidx.work]
```
`MinstrelApplication` implements `Configuration.Provider` and supplies `HiltWorkerFactory`, but the work-runtime library auto-registers `WorkManagerInitializer` via androidx-startup, racing the on-demand path. Lint catches this as a release blocker. AOSP-recommended fix: merge the `InitializationProvider` entry and remove the nested `WorkManagerInitializer` meta-data with `tools:node="remove"`.
After merge I'll force-move `v2026.06.01` to the new main HEAD; the workflow `concurrency: cancel-in-progress` will kill the in-flight tag runs from the broken HEAD.
The android.yml release build (run 110, job 282) failed at
lintVitalRelease with:
AndroidManifest.xml:13: Error: Remove androidx.work.WorkManagerInitializer
from your AndroidManifest.xml when using on-demand initialization.
[RemoveWorkManagerInitializer from androidx.work]
MinstrelApplication implements androidx.work.Configuration.Provider
and supplies the HiltWorkerFactory, so WorkManager initializes
on-demand at first WorkManager.getInstance(...) call. The androidx-
startup InitializationProvider that ships with the work-runtime
library still auto-registers WorkManagerInitializer, racing the
on-demand path. Lint catches this as a release blocker.
Fix: merge the InitializationProvider entry and remove the nested
WorkManagerInitializer meta-data with tools:node='remove'. This is
the AOSP-recommended fix when an Application is its own
Configuration.Provider.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fast-follow on the Dockerfile fix. The next failure in the v2026.06.01 chain:
android.ymlrelease build (run 110, job 282) failed atlintVitalRelease:MinstrelApplicationimplementsConfiguration.Providerand suppliesHiltWorkerFactory, but the work-runtime library auto-registersWorkManagerInitializervia androidx-startup, racing the on-demand path. Lint catches this as a release blocker. AOSP-recommended fix: merge theInitializationProviderentry and remove the nestedWorkManagerInitializermeta-data withtools:node="remove".After merge I'll force-move
v2026.06.01to the new main HEAD; the workflowconcurrency: cancel-in-progresswill kill the in-flight tag runs from the broken HEAD.