From 4ba53b717908265a34d1677def41ba8264a006f2 Mon Sep 17 00:00:00 2001
From: Manuel Polo <mistermx@gmail.com>
Date: Mon, 27 Jul 2026 11:28:13 +0200
Subject: [PATCH] chore: release 0.8.1

Ships the execute-poll fix for the 202 the API returns when a job is known but
its result is not readable yet.

api-client-java stays at 0.6.0: the generated signature does not move, because
openapi-generator takes the 200 type and ignores the 202 schema, and at runtime
any 2xx is a success. A 202 therefore arrives as a BacktestJobResult with a
null state, which is exactly what the fix in this release handles.

Verified against the live API serving that spec: full verify green, live
integration included.
---
 CHANGELOG.md | 2 ++
 pom.xml      | 2 +-
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 25da367..e6813c8 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,6 +6,8 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 
 ## [Unreleased]
 
+## [0.8.1] — 2026-07-27
+
 ### Fixed 🐛
 
 - **A `202` on the execute-result poll no longer ends the poll with an empty result.** The API
diff --git a/pom.xml b/pom.xml
index d574906..bef4289 100644
--- a/pom.xml
+++ b/pom.xml
@@ -6,7 +6,7 @@
 
     <groupId>com.qtsurfer</groupId>
     <artifactId>sdk-java</artifactId>
-    <version>0.8.0</version>
+    <version>0.8.1</version>
     <packaging>jar</packaging>
 
     <name>QTSurfer SDK</name>