Open the 3.0.1 development cycle

[wolpert]

v3.0.0 is out — tagged, GitHub release published, Java artifacts pushed to Maven Central. This moves the working versions on to 3.0.1.

Versions

File	Before	After
gradle.properties	3.0.0-SNAPSHOT	3.0.1-SNAPSHOT
hofmann-rust/Cargo.toml (+ Cargo.lock)	3.0.0	3.0.1
hofmann-typescript/package.json (+ lock)	3.0.0	3.0.1

How the Java version actually resolves

Worth recording, because it is not obvious. gradle.properties only supplies the version for untagged builds — settings.gradle.kts:41 overrides it from an exact-match git tag on HEAD:

gradle.beforeProject {
    val gitVersion = providers.exec { commandLine("git", "describe", "--tags", "--exact-match", "HEAD") }...
    if (gitVersion.isNotEmpty() && gitVersion.startsWith("v")) { version = matchResult.groupValues[1] }
}

So the v3.0.0 release build reported Using version from Git tag: 3.0.0 and passed the "Verify version matches tag" check even though gradle.properties said 3.0.0-SNAPSHOT. The -SNAPSHOT suffix in this file is purely a development marker and never reaches a release.

The Rust and TypeScript versions have no such indirection — they are literally what cargo publish and npm publish push, which is why they go to a plain 3.0.1.

Verification at 3.0.1

• Java — ./gradlew clean build succeeds; 609 tests, 0 failures, 0 skipped. ./gradlew properties reports 3.0.1-SNAPSHOT once HEAD is off the v3.0.0 tag.
• Rust — cargo fmt --all --check, cargo clippy --all-targets --locked -- -D warnings and cargo test --locked all clean. The --locked runs matter here: bumping the crate version rewrites Cargo.lock, and the rust job added in Build, lint and test hofmann-rust in CI #83 would fail on a stale one.
• TypeScript — npm ci, typecheck, build and test all pass.

🤖 Generated with Claude Code