Yicong-Huang opened a new pull request, #7068: URL: https://github.com/apache/texera/pull/7068
### What changes were proposed in this PR? `.github/renovate.json5` scoped and grouped **every** `amber/**` dependency bump as `pyamber`. But `.github/labeler.yml` treats `amber/` as two areas: the Scala engine (`amber/build.sbt`, ~80 versioned Scala deps) is labeled `engine`, and only the Python requirement manifests (`requirements*.txt`, `pyproject.toml`) are `pyamber`. So an amber Scala dependency PR landed a `chore(deps, pyamber)` commit while the labeler tagged it `engine`, and amber sbt minors were grouped into "pyamber minor updates" instead of staying individual like every other sbt minor. This splits the amber rules by Renovate manager: - `pip_requirements` → `deps, pyamber` (unchanged intent) - `sbt` → `deps, engine`, matching the labeler As a side effect amber sbt patches now fall through to the shared `sbt patch updates` group and amber sbt minors stay individual, matching the config's own stated intent for sbt minors. ### Any related issues, documentation, discussions? Closes #7067 ### How was this PR tested? - `renovate-config-validator` passes on the updated config. - Manually traced each amber manager/update-type against the labeler labels to confirm the scopes now align. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 4.8) -- 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]
