Repository navigation
docs: add integration guides and simplify latest release installation - #53
Merged
Merged
Conversation
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
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.
The README previously mixed client examples, overlapping compatibility summaries, and release commands that required manually choosing a version and platform. It now links every data tool to a setup guide and installs the latest published release by default.
:latestwith--pull=always; detect the binary platform, resolve the latest release tag, and verify the archive checksum before starting the server.Validation: local Markdown links and anchors checked across 18 files; all 14 README tool links verified; README shell and Python snippet syntax checked; Go example compiled;
git diff --checkpassed. Java compilation could not run because no JDK is installed. No integration suites or application tests were rerun, and no new compatibility passes are claimed.The latest-release metadata identified v0.1.0, but its download assets had not yet been attached when checked. The install section explains artifact publication and the source-build fallback; release installation was not exercised end to end.