SBPro
b28662d3b4
Breaking change. The monorepo's gitea host was previously inferred from the first target's subrepo_url, silently coupling the two and breaking on any multi-host setup (monorepo on host A, target on host B). v2.0.0 replaces the inference with a required josh.monorepo_url field that mirrors subrepo_url — same parsing, same SSH/HTTPS auth options, same shape. - schema_version: 2 is now required; v1 configs are rejected with a clear migration error - josh.monorepo_url is required; josh.monorepo_auth is optional (default https) - mono_auth_url() in lib/auth.sh mirrors subrepo_auth_url() - MONOREPO_API derives from monorepo_url's host instead of .[0].gitea_host; env-var override preserved as escape hatch - initial_import() and force-push call mono_auth_url() instead of building URLs inline - ADR-012 documents the rationale; CHANGELOG includes migration snippet Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
19 lines
425 B
YAML
19 lines
425 B
YAML
# Test fixture: minimal single-target config
|
|
schema_version: 2
|
|
josh:
|
|
proxy_url: "https://josh.test.local"
|
|
monorepo_path: "org/repo"
|
|
monorepo_url: "git@gitea.test.local:org/repo.git"
|
|
|
|
targets:
|
|
- name: "example"
|
|
subfolder: "services/example"
|
|
subrepo_url: "https://gitea.test.local/ext/example.git"
|
|
branches:
|
|
main: main
|
|
|
|
bot:
|
|
name: "test-bot"
|
|
email: "test@test.local"
|
|
trailer: "Josh-Sync-Origin"
|