panates / rman / 39608132105

95%

main: 95%

push

github

feat(publish): spm target - publish to the SyncBridge registry through the repository's spm

A package naming "spm" in its publish.target is published with the
repository's own spm (@syncbridge/syncbuild, >= 2.2.0), the way the npm
target goes through npm. Built in rather than shipped by syncbuild: rman
already carries the npm registry's half, and the SyncBridge registry is the
same kind of thing and ours. What rman needs from spm is asked of spm -
`spm view --json` and `spm publish --no-wait` were added to syncbuild for it.

- Plan: `spm view <name> --json` - up-to-date when the version is listed,
  publish when not. A failed lookup is an error with spm's own reason, never
  "not published".
- Apply: `spm publish --skip-existing` in the package directory, output on
  stderr so `--json` stays one document; a version spm skipped reads
  up-to-date. In GitHub Actions spm publishes as the job through OIDC.
  Unattended elsewhere (no TTY) it is told `--no-wait`, and its exit code 3
  becomes a reason saying where to publish from instead of a ten-minute wait.
- `publish.spm.access` / `.registry`, `--spm-access` / `--spm-registry` -
  prefixed because npm already declares `--access` and `--registry`.

Asked for by syncbridge-io/public-modules. Measured against production with
syncbuild 2.2.0: `spm view` answers `{"versions":[]}` and the plan reads
"publish - never published"; an unreachable registry plans as an error
carrying "could not be reached: bad port".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

4676 of 5113 branches covered (91.45%)

Branch coverage included in aggregate %.

315 of 320 new or added lines in 5 files covered. (98.44%)

24824 of 25962 relevant lines covered (95.62%)

263.82 hits per line