dongjoon-hyun opened a new pull request, #800: URL: https://github.com/apache/spark-kubernetes-operator/pull/800
### What changes were proposed in this pull request? This PR regenerates `gradle/verification-metadata.xml` from scratch to drop stale entries: ```bash rm gradle/verification-metadata.xml gradle --write-verification-metadata sha512 build --refresh-dependencies ``` Since `--write-verification-metadata` is append-only, the checked-in file accumulated entries that are no longer recorded. The regeneration removes 31 artifact entries (987 → 956) and adds none: - 30 `.pom` entries of components that also publish Gradle Module Metadata. Gradle uses the `.module` file as the descriptor for those components, so the sibling `.pom` is never verified. Each component keeps its `.module` entry. - 1 `junit-bom-6.0.2.module` entry, which is genuinely stale since only `junit-bom` 6.0.3 / 6.1.x are resolved today. No `.jar` checksum is removed and no dependency version is changed. ### Why are the changes needed? To keep the dependency verification metadata in sync with the actual dependency set, so that leftovers don't show up as noise in future dependency upgrade diffs. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass the CIs and `gradle build` locally with `verify-metadata=true` enabled. The pruned file was also validated against an empty `GRADLE_USER_HOME` to force a cold re-download of all dependencies. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Opus 5 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
