Repository navigation
Commit 1696cda
fix(cd): compute the first fork RC without a tag that does not exist
The first CD run after the release work merged failed:
Latest release: fork-v0.0.0
fatal: ambiguous argument 'fork-v0.0.0..HEAD': unknown revision
With no fork-v tag yet, the job synthesised "fork-v0.0.0" as a starting point for
the version arithmetic and then fed that same string to git log as a ref. It is
not one. Every RC would have failed until the first stable release existed —
which itself requires a working release path.
Separates the two concerns: 0.0.0 is the version baseline, and the commit range
is all of history when there is no tag to start from.
The prior isolated test of this logic passed because it only exercised the
version maths, never the git log that consumes its output. Verified this time by
running the real branch logic against the real repository:
kylehgc/rtk: base=0.0.0 range=HEAD -> fork-dev-0.1.0-rc.N
rtk-ai/rtk: base=0.44.1 range=v0.44.1..HEAD -> dev-0.45.0-rc.N
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>1 parent 17dd0d3 commit 1696cda
1 file changed
Lines changed: 15 additions & 10 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
93 | 93 | | |
94 | 94 | | |
95 | 95 | | |
96 | | - | |
97 | | - | |
98 | | - | |
99 | | - | |
100 | | - | |
101 | | - | |
102 | | - | |
| 96 | + | |
| 97 | + | |
| 98 | + | |
| 99 | + | |
| 100 | + | |
| 101 | + | |
| 102 | + | |
| 103 | + | |
| 104 | + | |
| 105 | + | |
| 106 | + | |
| 107 | + | |
| 108 | + | |
| 109 | + | |
103 | 110 | | |
104 | | - | |
105 | | - | |
106 | 111 | | |
107 | 112 | | |
108 | | - | |
| 113 | + | |
109 | 114 | | |
110 | 115 | | |
111 | 116 | | |
| |||
0 commit comments