Repository navigation
Commit b383e3e
ci: serialize release creation so the upload matrix never races
Splits the tag release path in go.yml into two stages:
- create-release: a single job (needs build) that ensures the GitHub release
for the tag exists before any assets are uploaded, so exactly one job owns
release creation.
- upload-assets: the existing 5-way build matrix (needs create-release) that
builds each binary plus its .sha256 and only adds files to the already
existing release.
This removes the concurrent-create race where all five matrix jobs tried to
create the same release. It worked on action-gh-release@v2 only by luck and
failed on @V3 with "already_exists (tag_name)". With creation serialized, v3
is safe to adopt.
Preserves the same 5 platform targets, asset names, 10 total assets (5 binaries
plus 5 .sha256), checksum generation, GITHUB_TOKEN usage, and contents: write
only on the release stages. Still on @v2 in this commit; the @V3 bump lands
separately after validation.
Co-authored-by: Cursor <cursoragent@cursor.com>1 parent 2c5e980 commit b383e3e
1 file changed
Lines changed: 26 additions & 10 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
45 | 45 | | |
46 | 46 | | |
47 | 47 | | |
48 | | - | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
49 | 54 | | |
50 | 55 | | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
51 | 69 | | |
52 | 70 | | |
53 | 71 | | |
| |||
113 | 131 | | |
114 | 132 | | |
115 | 133 | | |
116 | | - | |
117 | | - | |
118 | | - | |
119 | | - | |
120 | | - | |
121 | | - | |
122 | | - | |
123 | 134 | | |
124 | 135 | | |
125 | 136 | | |
126 | 137 | | |
127 | | - | |
| 138 | + | |
| 139 | + | |
| 140 | + | |
| 141 | + | |
128 | 142 | | |
129 | 143 | | |
130 | | - | |
| 144 | + | |
| 145 | + | |
| 146 | + | |
131 | 147 | | |
132 | 148 | | |
0 commit comments