Closed wzieba closed 3 weeks ago
1 Warning | |
---|---|
:warning: | PR is not assigned to a milestone. |
Generated by :no_entry_sign: Danger
The following changes in project dependencies were detected (configuration wordpressVanillaReleaseRuntimeClasspath
):
App Name | WordPress | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr21353-cfa1d78 | |
Commit | cfa1d78ab732c94c80b376840cf04312e3ab9720 | |
Direct Download | wordpress-prototype-build-pr21353-cfa1d78.apk |
App Name | Jetpack | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr21353-cfa1d78 | |
Commit | cfa1d78ab732c94c80b376840cf04312e3ab9720 | |
Direct Download | jetpack-prototype-build-pr21353-cfa1d78.apk |
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
👍 on https://github.com/wordpress-mobile/WordPress-Android/pull/21353#issuecomment-2435711726, but also, me seeing dagger pointing to 2.52, it made me wonder why... Only to then understand that this is coming from the login module. Having the dagger version being driven by this module instead of version catalogs seems a bit odd, right. On a separate PR, do you maybe have any plans to move these version into version catalogs as well? 🤔
FYI: This work is actually being address here: #21367 ✅
Description
This PR adds several, post FluxC vendor improvements:
*/wc/*
WireMock files that are simply not needed (I should've exclude them during migration but I haven't noticed them)gradle.properties-example
of vendored modulesfluxc
modules to use local version catalog instead of shared dependency catalog As with the FluxC merge, this doesn't seem to add many benefits and makes updating dependencies and keeping consise dependency tree more difficult.Testing
This is build-focus work. Green light from CI is completely fine. Mind the dependency diff tree comment: this PR shouldn't introduce changes to the runtime classpath.