Skip to content

Build: Strict runtime-deps check and auto-regeneration for dependabot PRs#16233

Open
kevinjqliu wants to merge 2 commits intoapache:mainfrom
kevinjqliu:kevinjqliu/strict-runtime-deps
Open

Build: Strict runtime-deps check and auto-regeneration for dependabot PRs#16233
kevinjqliu wants to merge 2 commits intoapache:mainfrom
kevinjqliu:kevinjqliu/strict-runtime-deps

Conversation

@kevinjqliu
Copy link
Copy Markdown
Contributor

Summary

checkRuntimeDeps previously ignored patch-level version changes (e.g. 5.6.0 → 5.6.1), allowing stale runtime-deps.txt baselines to pass CI. This caused PRs like #16204 to merge without updating the baselines.

Changes

  1. runtime-deps.gradle: Remove patch tolerance — compare exact versions so any mismatch fails the build.
  2. .github/workflows/autoupdate-runtime-deps.yml (new): Auto-regenerate and commit runtime-deps.txt on dependabot PRs that modify gradle/libs.versions.toml.

Testing

  • Verified checkRuntimeDeps fails on a patch-level version mismatch (httpclient5 5.6.0 vs 5.6.1).
  • Verified checkAllRuntimeDeps passes with current baselines.

@kevinjqliu
Copy link
Copy Markdown
Contributor Author

i was surprised by the drift in runtime-deps.txt, @RussellSpitzer wydt about this pattern to autoupdate for dependabot?

@kevinjqliu kevinjqliu requested a review from RussellSpitzer May 6, 2026 21:01
@RussellSpitzer
Copy link
Copy Markdown
Member

@kevinjqliu Ryan and I discussed this in the previous work. Rather than letting dependapot automatically change the deps (or raise the change) we just decided to ignore patch updates. I still record them though so it may make sense to remove them

@RussellSpitzer
Copy link
Copy Markdown
Member

I think I would vote that we just drop the patch's from the dependency text to avoid the churn there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants