Decisions, architecture and roadmap for Bitborg.
| Filnamn | Senaste incheckningsmeddelande | Senaste incheckningsdatum |
|---|---|---|
## What A package rule gives lock-file maintenance `prPriority: 1` in the shared preset. ## Why `RenovateUpdateHeldTooLong` fired again for bitborg-web (`renovate/lock-file-maintenance` and `renovate/drizzle-orm-0.x`, both held since 2026-09-22). - `prConcurrentLimit` is 6 and `branchConcurrentLimit` falls back to it. Existing branches count toward the limit. - On 2026-09-28 a stale `renovate/sharp-0.x` branch still existed (bitborg-web PR #226 merged, never deleted, so Renovate would not prune it). Only five new branches fit. - Renovate sorts by `prPriority`, then update type, with lock-file maintenance last. It is the first to starve whenever six or more updates are eligible. The `branch-limit-reached` decision logs at debug only, so production logs were silent. - The same mechanism fits bitborg-infra#487: on 2026-09-21 exactly six PRs were created, and lock-file maintenance was the sixth. The stale branches were deleted on 2026-10-02, so drizzle-orm should clear on the next Monday run without this change. Lock-file maintenance needs the priority. ## Not changed The limit of 6 stays: a bigger Monday burst queues more CI jobs against the runner cap. Raising it is the alternative if other updates also starve. ## Test `renovate-config-validator --strict` passes. The sort order was read from Renovate 43 (`workers/repository/process/sort.js`): `prPriority` descending comes before update type. Co-authored-by: Johannes <445378+supernaut@users.noreply.github.com> Reviewed-on: #115 |
||
| .forgejo/workflows | ||
| .vscode | ||
| contributing | ||
| decisions | ||
| design | ||
| .gitignore | ||
| .markdownlint-cli2.jsonc | ||
| .prettierignore | ||
| architecture.md | ||
| automerge-safe.json | ||
| default.json | ||
| lefthook.json | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| principles.md | ||
| README.md | ||
| renovate.json | ||
bitborg-docs
Decisions, architecture and roadmap for Bitborg.
- Architecture:
architecture.md - Guiding principles:
principles.md - Decisions (ADRs):
decisions/ - Cross-cutting design:
design/ - Roadmap: the Bitborg Roadmap board — direction & sequencing — with epics filed as issues in this repo.
- Contributing / issue tracking:
contributing/issue-tracking.md
Repo-specific operational docs (running OpenTofu/Ansible) live in
bitborg-infra.