ci(publish): auto-confirm opam publish via OPAMCONFIRMLEVEL=unsafe-yes

[grootstebozewolf]

Summary

The spatial-algebra-v0.1.2 / robust-predicates-v0.1.1 releases were green and their tarballs attached, but the coq/opam PRs did not open. Logs show opam-publish auto-answered no:

+ yes
+ opam publish --no-browser --repo=coq/opam ...
  - coq-spatial-algebra version 0.1.2 ...
Please confirm the above data. Continue ?  [Y/n] n

opam-publish's confirm checks whether stdin is a tty; in CI it isn't, so the piped yes (and OPAMYES) were ignored and it defaulted to no.

Fix

Use opam's documented non-interactive mechanism, OPAMCONFIRMLEVEL=unsafe-yes, which auto-answers every confirmation without reading input. Drops the yes | pipe and its pipefail handling.

State / honesty

• This is the correct mechanism per opam docs, but it can't be dry-run here — it'll be verified only by the next release. opam-publish remains best-effort: if it still won't confirm, the run stays green with the tarball attached + the manual command in the job summary.
• Both existing releases already have their tarballs; only the opam-repo PRs are outstanding. After merge, a fresh tag (*-v0.1.3 / *-v0.1.2) runs the corrected path. (A manual one-liner can also open them immediately from the attached tarballs.)

🤖 Generated with Claude Code

---

Generated by Claude Code