Commit 9277e0f
committed
🐛 fix(ci): main builds compute fresh CalVer and tag locally before Gradle
PR #4 broke the release workflow: Gradle's tag-driven version derivation
expects an exact-match tag at HEAD, but on main there isn't one until
the release job creates it. Result: git describe returned the post-tag
dev format (e.g. v2026.05.08.30-1-g1be0321) and the release action used
that string verbatim as the new tag and Release name.
Fix: split the Compute version step. On refs/heads/main, compute a fresh
CalVer from date + GITHUB_RUN_NUMBER and `git tag` HEAD locally so
Gradle's git-describe finds an exact match. The release job then pushes
this tag when creating the GitHub Release. PR / feature-branch builds
keep using `git describe` for artifact-naming purposes.
The bad tag/release v2026.05.08.30-1-g1be0321 has been deleted.1 parent aace637 commit 9277e0f
1 file changed
Lines changed: 16 additions & 7 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
55 | 55 | | |
56 | 56 | | |
57 | 57 | | |
58 | | - | |
59 | | - | |
60 | | - | |
61 | | - | |
62 | | - | |
63 | | - | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
64 | 74 | | |
65 | | - | |
66 | 75 | | |
67 | 76 | | |
68 | 77 | | |
| |||
0 commit comments