The GitHub Actions job "Required Checks" on texera.git/gh-readonly-queue/main/pr-7068-f303f05c6e873a13c0f3b27f116aa3b6db2b8f86 has succeeded. Run started by GitHub user Yicong-Huang (triggered by Yicong-Huang).
Head commit for run: 40caed3adb048b57a2a42556fccda128439881b6 / Yicong Huang <[email protected]> ci: align renovate amber scopes (amber vs pyamber) (#7068) ### What changes were proposed in this PR? `.github/renovate.json5` scoped and grouped **every** `amber/**` dependency bump as `pyamber`. But `amber/` holds both the Scala engine and the Python (pyamber) worker: `amber/build.sbt` alone declares ~80 versioned Scala deps. So an amber Scala dependency PR landed a `chore(deps, pyamber)` commit even though it is not a Python change, 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, amber` (the directory's own name, not the Python-specific one) 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 through the rules to confirm Scala bumps now scope `amber` and Python bumps stay `pyamber`. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 4.8) Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]> Report URL: https://github.com/apache/texera/actions/runs/30499175618 With regards, GitHub Actions via GitBox
