janhoy opened a new pull request, #4581:
URL: https://github.com/apache/solr/pull/4581
Renovate currently files dependency PRs **every Sunday**, producing more
than a hundred tiny individual PRs that are a lot of work to review and merge.
Since Solr only releases every couple of months, this cadence and granularity
is more than we need.
This PR reworks `.github/renovate.json` to cut that churn.
### Changes
- **Schedule: weekly → monthly** (`before 9am on the first day of the
month`). An RM can
temporarily switch back to weekly a few weeks before a release. Redundant
per-group
monthly schedules were removed.
- **Two catch-all buckets** collapse the long tail of unrelated libraries:
minor/patch bumps
land in `all non-major dependencies` / `all non-major test dependencies`.
**Major bumps are
never bundled** — each still gets its own PR for individual review.
- **12 logical groups** derived from how libraries are actually wired in the
build (shared
BOMs / version keys / cross-module coupling), so version-compatible
artifacts always move together:
- **Admin UI** — the `solr/ui` KMP/Compose stack (compose, androidx,
kotlin(x), decompose,
essenty, mvikotlin, ktor, kotlin-logging)
- **Web server stack** — Jetty + Jakarta EE + Jersey + HK2
(`jersey-container-jetty-http`)
- **gRPC and Netty** — gRPC + Netty (its transport) + protobuf; shared by
OTel and GCS
- **Telemetry** — OpenTelemetry + the Prometheus libs it exports to
- **Google Cloud** — cloud/api/auth client stack (kept apart from the gRPC
transport it consumes)
- **Jackson & Woodstox**, **Logging** (Log4j + SLF4J + Disruptor),
**ZooKeeper & Curator**,
**Calcite**, **Apache HttpComponents**, **AWS SDK**, **OkHttp & Okio**,
**GitHub Actions**
- Lucene (follows the Lucene release) and **jetty major** bumps (done
manually) remain excluded.
- `dev-docs/dependency-upgrades.adoc` updated to document the new cadence
and grouping.
Rule ordering: catch-alls → logical groups override → `enabled:false` skips
win last.
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
