release: one version number, bumped by a script and checked by CI - #76
Merged
Conversation
scripts/bump_version.py treats project(VERSION) in CMakeLists.txt as the source of truth. --set rewrites the ten manifests that carry the release number (the Python, Rust, C# and Java packages, the driver's own version string, the Rust lock file) and the install snippets in ten docs; --check verifies they all agree, and --check --tag that a git tag names the same version. The tests/ and bench/ manifests have versions of their own and are left alone; ROADMAP, the FAQ and the benchmark files record history and keep their numbers. CI runs --check on every push and pull request (a "Version agreement" job); the Release workflow runs it against the tag before creating the release or building an asset. RELEASING.md is the checklist: bump, tag, publish each registry by hand, verify each one, then site and announcements. Why now: 0.1.0 is spelled out in 20 files, no tooling kept them together, and 0.1.1 is about to ship. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YG6wFApZpg2xe61EmKhaSZ
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Groundwork for 0.1.1 and every release after it.
scripts/bump_version.py—project(VERSION)in CMakeLists.txt is the source of truth.--set X.Y.Zrewrites the ten manifests that carry the release number (Python, Rust + lock, C#, Java, both copies of the driver's version string) and the install snippets in ten docs.--checkverifies they agree;--check --tag vX.Y.Zalso checks a git tag. Dry-run of--set 0.1.1touches 20 files, 45 lines, and--checkpasses afterwards. tests/ and bench/ keep their own manifest versions; ROADMAP, FAQ and benchmark files keep their history.--checkon every push and PR.--check --tagagainst the pushed tag before creating the release or building anything, so a half-bumped tag fails in seconds.RELEASING.md: the checklist — bump, tag (v*andgo/v*), publish each registry by hand (PyPI/NuGet/Maven workflows,cargo publish, Go proxy), verify each with a one-liner, then site and announcements.No version changes in this PR; the 0.1.1 bump follows as its own PR once this is in.
🤖 Generated with Claude Code
https://claude.ai/code/session_01YG6wFApZpg2xe61EmKhaSZ