mirror of
https://github.com/hanzoai/java-sdk.git
synced 2026-10-30 15:07:36 +00:00
zooqueenandHanzo Dev
fb2ed33d11
The 09-06 regeneration renamed AgentsApi and ToolsApi to AgentApi and ToolApi and the examples kept the old names, so examples-build failed on main. hanzoai/ci gates a client-lane move on that same test, so every release dispatch since has stopped before regenerating and the jar stayed at 8.5.156, a client with no postDecisions. The client is regenerated from the document api.hanzo.ai serves (hanzo-inc/cloud 151878a3c, sha256 00564264), which now namespaces its schemas (AgentAgentView, ProvisioningProvisionRequest, ToolToolList) and types chat completions, so the examples are rewritten against it: agent, store and tools use the new names and paths, and chat sends a prompt and prints the reply instead of a status. .spec-lock is left to the lane, whose next move records the ref it was handed. hanzo.yml now names where the version lives, scripts/version, so the cut rewrites build.gradle to the release number and the push to main publishes it through release.yml; without it the cut tagged a build.gradle Central already served and nothing published. The README names the 8.5 line (8.5.+, [8.5,8.6)) rather than a patch, because each release cuts a patch into build.gradle alone, and scripts/readme checks the line instead of a number that goes stale. Co-authored-by: Hanzo Dev <[email protected]>
8 lines
347 B
Bash
Executable File
8 lines
347 B
Bash
Executable File
#!/bin/sh
|
|
# Print the version hanzo-java-cloud/build.gradle publishes. The one reader of
|
|
# it: hanzoai/ci's cut (hanzo.yml client.version), the readme gate and the
|
|
# release workflow all ask this script, so none of them parses the file its own way.
|
|
set -eu
|
|
cd "$(dirname "$0")/.."
|
|
sed -n "s/^version = '\(.*\)'/\1/p" hanzo-java-cloud/build.gradle
|