You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* fix(manifest): recognize Gradle's alternate no-matching-variant phrasings
Gradle phrases a zero-compatible-variant failure several ways depending on
version and whether consumer attributes were supplied. The classifier only
matched "no matching variant"/"no variants of", so "unable to find a
matching variant" and "no compatible variant" fell through to the generic
"other" category. Severity was unaffected (both blocking), but the report
rendered under the wrong header; recognize the alternate phrasings so these
surface under the accurate "No compatible variant" heading.
* feat(manifest): unify Gradle config-level resolution transparency
A whole Gradle configuration whose resolution throws (as opposed to a single
unresolved dependency within it) was previously caught and logged to stdout but
never surfaced: it still counted as "scanned", so the user was never told we
could not scan it.
Record such configs as a new `unscannable` fact and classify them by the same
cause rules as per-dependency failures: variant ambiguity stays lenient (a
one-line notice), every other cause is fail-closed (blocking, overridable by
--ignore-unresolved). The build script still exits cleanly and the TS layer
owns the reporting; a config-level failure no longer trips the crashed-build
path, which stays reserved for a build that produced nothing at all.
Also drop the stale "--include-configs default excludes AGP instrumented-test
classpaths" help text: the native-facts rewrite removed that exclusion, and
AGP AndroidTest configs resolve like any other.
* docs(changelog): note Gradle unscannable-config transparency under Unreleased
* fix(manifest): address review nits on config-transparency report
- Don't lead the failure summary with a blank line when there are only blocking
unscannable configs and no per-dependency failures (avoids a dangling marker
under logger.fail); added a regression assertion.
- Correct the config-throw comments: the path fires on config-LEVEL failures
(resolution-rule throws, artifact-transform failures, broken repos), not AGP
*AndroidTest* configs, which resolve cleanly per the validation.
'When generating facts: comma-separated glob patterns matched against Gradle configuration names (case-sensitive, `*` and `?` wildcards). Only configurations matching at least one pattern are resolved. e.g. `*CompileClasspath,*RuntimeClasspath`. Default: every resolvable configuration except AGP instrumented-test classpaths',
48
+
'When generating facts: comma-separated glob patterns matched against Gradle configuration names (case-sensitive, `*` and `?` wildcards). Only configurations matching at least one pattern are resolved. e.g. `*CompileClasspath,*RuntimeClasspath`. Default: every resolvable configuration',
--facts Emit a Socket facts JSON file (\`.socket.facts.json\`) describing the resolved dependency graph. This is the default; pass \`--pom\` to generate \`pom.xml\` files instead
29
29
--gradle-opts Additional options to pass on to ./gradlew, see \`./gradlew --help\`
30
30
--ignore-unresolved When generating facts: warn on unresolved dependencies instead of failing the run (unresolved deps are not emitted to the facts file)
31
-
--include-configs When generating facts: comma-separated glob patterns matched against Gradle configuration names (case-sensitive, \`*\` and \`?\` wildcards). Only configurations matching at least one pattern are resolved. e.g. \`*CompileClasspath,*RuntimeClasspath\`. Default: every resolvable configuration except AGP instrumented-test classpaths
31
+
--include-configs When generating facts: comma-separated glob patterns matched against Gradle configuration names (case-sensitive, \`*\` and \`?\` wildcards). Only configurations matching at least one pattern are resolved. e.g. \`*CompileClasspath,*RuntimeClasspath\`. Default: every resolvable configuration
32
32
--pom Generate \`pom.xml\` manifest file(s) instead of the default Socket facts file (\`.socket.facts.json\`)
'When generating facts: comma-separated glob patterns matched against Gradle configuration names (case-sensitive, `*` and `?` wildcards). Only configurations matching at least one pattern are resolved. e.g. `*CompileClasspath,*RuntimeClasspath`. Default: every resolvable configuration except AGP instrumented-test classpaths',
53
+
'When generating facts: comma-separated glob patterns matched against Gradle configuration names (case-sensitive, `*` and `?` wildcards). Only configurations matching at least one pattern are resolved. e.g. `*CompileClasspath,*RuntimeClasspath`. Default: every resolvable configuration',
--facts Emit a Socket facts JSON file (\`.socket.facts.json\`) describing the resolved dependency graph. This is the default; pass \`--pom\` to generate \`pom.xml\` files instead
29
29
--gradle-opts Additional options to pass on to ./gradlew, see \`./gradlew --help\`
30
30
--ignore-unresolved When generating facts: warn on unresolved dependencies instead of failing the run (unresolved deps are not emitted to the facts file)
31
-
--include-configs When generating facts: comma-separated glob patterns matched against Gradle configuration names (case-sensitive, \`*\` and \`?\` wildcards). Only configurations matching at least one pattern are resolved. e.g. \`*CompileClasspath,*RuntimeClasspath\`. Default: every resolvable configuration except AGP instrumented-test classpaths
31
+
--include-configs When generating facts: comma-separated glob patterns matched against Gradle configuration names (case-sensitive, \`*\` and \`?\` wildcards). Only configurations matching at least one pattern are resolved. e.g. \`*CompileClasspath,*RuntimeClasspath\`. Default: every resolvable configuration
32
32
--pom Generate \`pom.xml\` manifest file(s) instead of the default Socket facts file (\`.socket.facts.json\`)
0 commit comments