(texera) 01/01: ci: align renovate amber scopes (amber vs pyamber) (#7068)

[gi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

github-merge-queue[bot] pushed a commit to branch gh-readonly-queue/main/pr-7068-f303f05c6e873a13c0f3b27f116aa3b6db2b8f86
in repository https://gitbox.apache.org/repos/asf/texera.git

commit 40caed3adb048b57a2a42556fccda128439881b6
Author: Yicong Huang <17...@users.noreply.github.com>
AuthorDate: Wed Jul 29 19:19:36 2026 -0400

    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) <no...@anthropic.com>
---
 .github/renovate.json5 | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/.github/renovate.json5 b/.github/renovate.json5
index 3f4f523ea4..c6fe7f387a 100644
--- a/.github/renovate.json5
+++ b/.github/renovate.json5
@@ -73,10 +73,20 @@
       matchFileNames: ['bin/y-websocket-server/**'],
       semanticCommitScope: 'deps, y-websocket-server',
     },
+    // amber/ holds both the Scala engine and the Python (pyamber) worker,
+    // so the old blanket `pyamber` scope mislabeled Scala bumps. Split by
+    // manager: Python requirement bumps stay `pyamber`, Scala (sbt) bumps
+    // get `amber` (the directory's own name, not the Python-specific one).
     {
       matchFileNames: ['amber/**'],
+      matchManagers: ['pip_requirements'],
       semanticCommitScope: 'deps, pyamber',
     },
+    {
+      matchFileNames: ['amber/**'],
+      matchManagers: ['sbt'],
+      semanticCommitScope: 'deps, amber',
+    },
 
     // Patch bumps grouped into one weekly PR per area. Minor bumps are
     // also grouped per area — except sbt, where minors ship behavior
@@ -104,6 +114,7 @@
     },
     {
       matchFileNames: ['amber/**'],
+      matchManagers: ['pip_requirements'],
       matchUpdateTypes: ['patch'],
       groupName: 'pyamber patch updates',
     },
@@ -134,6 +145,7 @@
     },
     {
       matchFileNames: ['amber/**'],
+      matchManagers: ['pip_requirements'],
       matchUpdateTypes: ['minor'],
       groupName: 'pyamber minor updates',
     },