Skip to content

Commit ca3ea69

Browse files
wolpertclaude
andcommitted
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_01XRQsssyhNo8aq4h7xASTXu
1 parent b9cfa44 commit ca3ea69

2 files changed

Lines changed: 6 additions & 5 deletions

File tree

RELEASING.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -86,14 +86,15 @@ right.
8686

8787
### Afterwards
8888

89-
Two files carry a version number and both need bumping:
89+
Two files carry a version number, and they move in opposite directions:
9090

91-
- `gradle.properties` — to the next `-SNAPSHOT`, e.g. `version=1.0.1-SNAPSHOT`
92-
- `README.md` — the dependency snippets near the top
91+
- `gradle.properties`forward, to the next `-SNAPSHOT`: after releasing 1.0.0, `1.0.1-SNAPSHOT`
92+
- `README.md` — the dependency snippets should name the version you *just released*, not the next one
9393

9494
Nothing enforces either. The first buys that a build from `main` is never mistakable for a build of
9595
the version that just shipped. The second is what a reader copies, and the Maven Central badge above
96-
the snippet is there so a stale number is visibly stale rather than quietly wrong.
96+
the snippet reads the real latest version, so a stale number is visibly stale rather than quietly
97+
wrong.
9798

9899
## One-time setup
99100

gradle.properties

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,4 +10,4 @@ org.gradle.parallel=true
1010
# this after a release, not before one.
1111
#
1212
group=com.codeheadsystems
13-
version=1.0.0-SNAPSHOT
13+
version=1.0.1-SNAPSHOT

0 commit comments

Comments
 (0)