fix(release): accept internal Forgejo origin for tag push #1463

Merged
coilyco-ops merged 1 commit from issue-1460 into main 2026-07-15 14:08:16 +00:00
Member

Release tagging now accepts both Forgejo's internal HTTP origin and the existing HTTPS origin when pushing the release tag, and the contract tests exercise both paths without logging the token.

  • Added HTTP/HTTPS push URL support in scripts/release-tag.sh.
  • Added regression coverage for both remote schemes plus the no-secret log constraint.
  • Verified with go test ./....

closes #1460
ward.workflow: pull-request-and-merge

Release tagging now accepts both Forgejo's internal HTTP origin and the existing HTTPS origin when pushing the release tag, and the contract tests exercise both paths without logging the token. - Added HTTP/HTTPS push URL support in `scripts/release-tag.sh`. - Added regression coverage for both remote schemes plus the no-secret log constraint. - Verified with `go test ./...`. closes #1460 ward.workflow: pull-request-and-merge
fix(release): accept internal forgejo origin
All checks were successful
test / test (pull_request) Successful in 1m5s
06501939fa
Sign in to join this conversation.
No description provided.