ai/mission-control
Watch
1
0
Fork
You've already forked mission-control
 0
Code Issues 4 Pull requests 7 Projects Releases 91 Packages 2 Wiki Activity

fix(ci): accept releases published from a main-targeted draft #45

Merged
morten-olsen merged 1 commit from fix/deploy-release-branch-target into main 2026-10-08 19:25:21 +02:00
Conversation 0 Commits 1 Files changed 3 +21 -3
morten-olsen commented 2026-10-08 19:17:03 +02:00
Owner

Publishing the draftsman draft in the Forgejo UI keeps target_commitish: main (see v0.11.0, v0.11.1, v0.12.0; only v0.13.0 carries a SHA). deploy-release required the target to equal the pipeline SHA, so publishing the pending v0.14.0 draft would have failed with 'Release/tag source differs from both image publication workflows'.

The resolved tag commit, together with the main-ancestry check, is the source evidence. A target of main is now accepted. Any other target must still equal the tag commit; a different SHA or a different branch still fails.

Tests: a failing-first case for a main target and a rejection case for another branch. All 26 scripts tests pass. Pairs with #44 (OOM in the deploy-access install). Both are needed for v0.14.0 to deploy itself.

Publishing the draftsman draft in the Forgejo UI keeps `target_commitish: main` (see v0.11.0, v0.11.1, v0.12.0; only v0.13.0 carries a SHA). `deploy-release` required the target to equal the pipeline SHA, so publishing the pending v0.14.0 draft would have failed with 'Release/tag source differs from both image publication workflows'. The resolved tag commit, together with the main-ancestry check, is the source evidence. A target of `main` is now accepted. Any other target must still equal the tag commit; a different SHA or a different branch still fails. Tests: a failing-first case for a `main` target and a rejection case for another branch. All 26 scripts tests pass. Pairs with #44 (OOM in the deploy-access install). Both are needed for v0.14.0 to deploy itself.
fix(ci): accept releases published from a main-targeted draft
All checks were successful
ci/woodpecker/push/quality Pipeline was successful
Details
ci/woodpecker/pr/quality Pipeline was successful
Details
ci/woodpecker/pr/image-agent Pipeline was successful
Details
ci/woodpecker/pr/docs Pipeline was successful
Details
ci/woodpecker/push/docs Pipeline was successful
Details
ci/woodpecker/pr/image Pipeline was successful
Details
92c9ec746f
 
Publishing a draftsman draft in the Forgejo UI keeps target_commitish as
'main' (v0.11.x, v0.12.0), so deploy-release failed every such release with
'Release/tag source differs'. The resolved tag commit, checked against main
ancestry, is the source evidence; a branch target of main is now accepted and
any other target must still equal the tag commit.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ai/mission-control!45
No description provided.