You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@texera.apache.org by gi...@apache.org on 2026/07/29 23:35:49 UTC
(texera) branch main updated (f303f05c6e -> 42493c6d8e)
This is an automated email from the ASF dual-hosted git repository.
github-merge-queue[bot] pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/texera.git
from f303f05c6e fix(ci): type routine Renovate bumps as chore, drop [security] suffix (#7072)
new 40caed3adb ci: align renovate amber scopes (amber vs pyamber) (#7068)
new 42493c6d8e ci: skip contributor template check for renovate-bot's User account (#7062)
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.github/renovate.json5 | 12 ++++++++++++
.github/workflows/contributor-checks.yml | 8 +++++++-
2 files changed, 19 insertions(+), 1 deletion(-)
(texera) 02/02: ci: skip contributor template check for renovate-bot's User account (#7062)
Posted by gi...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
github-merge-queue[bot] pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/texera.git
commit 42493c6d8efa49d6dbef7121d1d78cf3d6036a7c
Author: Yicong Huang <17...@users.noreply.github.com>
AuthorDate: Wed Jul 29 19:22:41 2026 -0400
ci: skip contributor template check for renovate-bot's User account (#7062)
### What changes were proposed in this PR?
The `contributor-checks` job in
`.github/workflows/contributor-checks.yml` gates on
`github.event.sender.type != 'Bot'` so it won't nag automated PR/issue
openers about not following the contribution template.
That gate catches GitHub App bots (e.g. `dependabot[bot]`, whose account
`type` is `Bot`) but **not** Renovate, which on this repo runs under a
regular User account: `renovate-bot` has `type: User`, so it slips
through and gets the "the description doesn't follow our template"
warning on every dependency-update PR (example: #7060).
This PR excludes `renovate-bot` explicitly by login:
```yaml
if: >-
github.event.sender.type != 'Bot' &&
github.event.sender.login != 'renovate-bot'
```
### Any related issues, documentation, discussions?
Closes #7063.
Example of the false warning: #7060.
### How was this PR tested?
- Confirmed via the GitHub API that `renovate-bot` has `type: User` (not
`Bot`), which is why the existing `sender.type != 'Bot'` gate did not
exclude it.
- Validated the workflow YAML parses and the folded `if:` expression
resolves to the intended single-line condition.
- The change is confined to the job-level `if:` gate; no `run:` step or
untrusted-input interpolation is touched.
### Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Opus 4.8)
Co-authored-by: Claude Opus 4.8 (1M context) <no...@anthropic.com>
---
.github/workflows/contributor-checks.yml | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/.github/workflows/contributor-checks.yml b/.github/workflows/contributor-checks.yml
index 2f8592a4f8..e643859e03 100644
--- a/.github/workflows/contributor-checks.yml
+++ b/.github/workflows/contributor-checks.yml
@@ -51,7 +51,13 @@ permissions:
jobs:
contributor-checks:
- if: github.event.sender.type != 'Bot'
+ # Skip automated PR/issue openers. GitHub App bots (e.g. dependabot)
+ # have sender.type == 'Bot', but Renovate runs under a regular User
+ # account (`renovate-bot`, type: User) and would otherwise be nagged
+ # for not following the template, so exclude it explicitly by login.
+ if: >-
+ github.event.sender.type != 'Bot' &&
+ github.event.sender.login != 'renovate-bot'
runs-on: ubuntu-latest
steps:
# pull_request_target and issues both resolve to the trusted base
(texera) 01/02: ci: align renovate amber scopes (amber vs pyamber) (#7068)
Posted by gi...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
github-merge-queue[bot] pushed a commit to branch main
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',
},