Commit ca3ea69
Move main off the released version
1.0.0 is on Central and cannot be replaced, so a working tree that still builds
1.0.0 coordinates is a hazard rather than a convenience: an accidental
publishToMavenLocal now overwrites the released artifact in a developer's own
~/.m2 with different bytes, and every local build of main claims to be the thing
that shipped.
The version reported by the build did not change with this edit, and that is the
tag substitution working: HEAD still carried v1.0.0, so `git describe` won since
gradle.properties is only the fallback. It reads 1.0.1-SNAPSHOT from this commit
onward, because this commit is the first one that is not the tag.
RELEASING.md said to bump README alongside it, which was ambiguous enough to be
wrong -- the two numbers move in opposite directions. gradle.properties goes
forward to the next snapshot; the README snippets name the version that was just
released, which is what somebody copying them wants.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XRQsssyhNo8aq4h7xASTXu1 parent b9cfa44 commit ca3ea69
2 files changed
Lines changed: 6 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
86 | 86 | | |
87 | 87 | | |
88 | 88 | | |
89 | | - | |
| 89 | + | |
90 | 90 | | |
91 | | - | |
92 | | - | |
| 91 | + | |
| 92 | + | |
93 | 93 | | |
94 | 94 | | |
95 | 95 | | |
96 | | - | |
| 96 | + | |
| 97 | + | |
97 | 98 | | |
98 | 99 | | |
99 | 100 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
10 | 10 | | |
11 | 11 | | |
12 | 12 | | |
13 | | - | |
| 13 | + | |
0 commit comments