chore(renovate): opt in to the shared automerge-safe preset #22

Sammanfogat

supernaut sammanfogade 1 incheckning från chore/renovate-automerge-opt-in in i main

2026-08-09 19:55:22 +00:00

supernaut kommenterad

2026-08-09 19:36:57 +00:00

Ägare

Companion to bitborg-docs #81, which adds an opt-in automerge-safe Renovate preset to the shared config.

Extends it here. The qualifying condition is that a merge to main ships nothing: release.yml triggers on push: tags: v*, not on a merge, so a merged dependency PR builds and releases nothing until a human cuts a version tag. That tag remains the release gate and stays manual.

What this automerges, once #81 merges:

non-major devDependencies (the existing grouped PR)
the toolchain group — Node and pnpm, including the Containerfile base image
the weekly lock-file maintenance PR

All three are gated on the required ci status check passing, via automergeType: pr + platformAutomerge, so Forgejo does the merging. Runtime dependencies and all majors stay human-reviewed — majors are still held by major.dependencyDashboardApproval, and excluded from every automerge rule, since approving one means "open the PR", not "ship it".

The rationale for the qualifying condition is recorded in renovate.json itself, so a future reader does not have to re-derive why this repo is entitled to automerge and others are not.

Merge after bitborg-docs #81 — until the preset exists on main there, local>bitborg/bitborg-docs:automerge-safe will not resolve.

Companion to bitborg-docs #81, which adds an opt-in `automerge-safe` Renovate preset to the shared config. Extends it here. The qualifying condition is that a merge to `main` ships nothing: `release.yml` triggers on `push: tags: v*`, not on a merge, so a merged dependency PR builds and releases nothing until a human cuts a version tag. That tag remains the release gate and stays manual. What this automerges, once `#81` merges: - non-major `devDependencies` (the existing grouped PR) - the `toolchain` group — Node and pnpm, including the Containerfile base image - the weekly lock-file maintenance PR All three are gated on the required `ci` status check passing, via `automergeType: pr` + `platformAutomerge`, so Forgejo does the merging. Runtime `dependencies` and all majors stay human-reviewed — majors are still held by `major.dependencyDashboardApproval`, and excluded from every automerge rule, since approving one means "open the PR", not "ship it". The rationale for the qualifying condition is recorded in `renovate.json` itself, so a future reader does not have to re-derive why this repo is entitled to automerge and others are not. **Merge after bitborg-docs #81** — until the preset exists on `main` there, `local>bitborg/bitborg-docs:automerge-safe` will not resolve.

supernaut lade till 1 incheckning

2026-08-09 19:36:57 +00:00