Releases: rhesis-ai/rhesis-java
Releases · rhesis-ai/rhesis-java
v0.1.4
[0.1.4] - 2026-04-20
Fixed
expected_responseandlanguage_codegenerated by synthesizers are now serialized as direct fields onPromptinstead of being nested undermetadata. Previously the backend silently dropped them duringtestSets().create(...), so generated tests had no expected response on the platform (#3).MultiTurnSynthesizerno longer throwsNullPointerExceptionwhen the LLM omitsmin_turnsormax_turnsfrom a generated test. The values are now treated as optional and set tonullonTestConfiguration, matching the Python SDK's behaviour.Test.metadatanow correctly deserializes from the backend'stest_metadatafield (renamed on the server to avoid colliding with SQLAlchemy's reservedModel.metadata). Before this changetest.metadata()returnednullafter anytestSets().getTests(...)round-trip, matching an analogous bug the Python SDK already worked around.
Changed
Promptrecord gained two top-level fields —expectedResponse(JSONexpected_response) andlanguageCode(JSONlanguage_code) — and is now@JsonInclude(NON_NULL)so unset fields no longer appear in serialized output.- Removed the
rolefield fromPrompt. It was never part of the Rhesis platform API or the Python SDK and had no effect beyond bloating the JSON payload. The positional constructor now takes(id, content, expectedResponse, languageCode, metadata); callers usingPrompt.builder()only need to drop any.role(...)call.
v0.1.3
[0.1.3] - 2026-04-20
Release automation bootstrap. No user-facing SDK changes.
Changed
- Added an automated release workflow (
.github/workflows/release.yml) that bumps the version, generates theCHANGELOG.mdentry via Gemini, publishes to GitHub Packages, and creates the GitHub Release behind an approval gate. - Fixed Maven authentication in
.github/workflows/publish.ymlso manual publishes to GitHub Packages work; removed itsrelease: publishedtrigger to avoid duplicate deploys.