Commit b4cd279
chore(build): harden the version resolution the previous commit moved
Two review findings on the moved block, both pre-existing behavior the move
preserved verbatim; fixing them here keeps the move itself pure.
git describe now passes --exclude "v*-*" so a prerelease-shaped tag
(v0.9.0-rc1) is never read as a release: describe falls back to the last
stable tag and the existing arithmetic yields the usual next-patch SNAPSHOT.
No such tags exist in this repo today, so this changes nothing retroactively.
resolvedVersion is validated as MAJOR.MINOR.PATCH[-suffix] at settings
evaluation. sample/androidApp destructures exactly three toInt() components
out of project.version, so a blank or two-part version previously surfaced as
a bare NumberFormatException deep in that module; now configuration fails
immediately and names the offending value. Verified both ways:
-PVERSION_NAME=bogus fails with the new message, and the full gate
(spotlessCheck detektAll allTests apiCheck koverVerify) passes on the
git-derived version.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>1 parent 65e2a82 commit b4cd279
1 file changed
Lines changed: 11 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
35 | 35 | | |
36 | 36 | | |
37 | 37 | | |
38 | | - | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
39 | 41 | | |
40 | 42 | | |
41 | 43 | | |
| |||
57 | 59 | | |
58 | 60 | | |
59 | 61 | | |
| 62 | + | |
| 63 | + | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
60 | 70 | | |
61 | 71 | | |
62 | 72 | | |
| |||
0 commit comments