fix(release): accept internal Forgejo origin for tag push #1463
No reviewers
Labels
No labels
burndown-2026-06
pressure-test
sunday-sprint
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/ward!1463
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-1460"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
scripts/release-tag.sh.go test ./....closes #1460
ward.workflow: pull-request-and-merge