jschoubben 79777d0f78 gitea: keep the operator's own login on main's merge whitelist beside mesh-tools (ADR 0534 §2) ...

The operator merges by hand at the forge when the mesh's own path is stuck,
without changing a rule. The logins come from the trusted config value
main-mergers, merged into the runtime config both programs read.

2026-10-23 12:10:10 +02:00

..

agent-teams

Feature 57 (config and provisioning): release the catalogue, the reviewed release branch merged with main, on top of main

2026-10-16 09:42:45 +00:00

agent-token

One forge user, nox-agent, for every machine's agents' SSH pushes, each machine's key titled by machine (issue 991, ADR 0410)

2026-10-17 00:46:43 +00:00

forge

Anchor patch hunks as git apply does, refuse patches touching non-100644 files by their real mode, survive bare-CR context lines (issue 1604 review)

2026-10-21 09:52:10 +00:00

forge-account-provider

Let gitea read the image build module's keys, so its key is the builders' (issue 1703f)

2026-10-22 10:27:01 +02:00

npm-registry

gitea forge bundle: name the parent the forge used, match protection rules as the forge does, bound a commit's size and a search's time (issue 539)

2026-10-12 12:51:22 +02:00

repositories

gitea: keep the operator's own login on main's merge whitelist beside mesh-tools (ADR 0534 §2)

2026-10-23 12:10:10 +02:00