diff --git a/README.md b/README.md index 35b4542..fe598e4 100644 --- a/README.md +++ b/README.md @@ -38,12 +38,12 @@ Three install paths depending on your stack. qa.fanar fanar-core - 0.2.0-SNAPSHOT + 0.3.0-SNAPSHOT qa.fanar fanar-json-jackson3 - 0.2.0-SNAPSHOT + 0.3.0-SNAPSHOT ``` @@ -64,7 +64,7 @@ try (FanarClient client = FanarClient.builder().apiKey(System.getenv("FANAR_API_ qa.fanar fanar-spring-boot-4-starter - 0.2.0-SNAPSHOT + 0.3.0-SNAPSHOT ``` @@ -88,7 +88,7 @@ class MyController { qa.fanar fanar-spring-ai-starter - 0.2.0-SNAPSHOT + 0.3.0-SNAPSHOT ``` diff --git a/docs/PROJECT_STATE.md b/docs/PROJECT_STATE.md index 5553046..c0af7f3 100644 --- a/docs/PROJECT_STATE.md +++ b/docs/PROJECT_STATE.md @@ -5,12 +5,14 @@ ## Phase -**0.2.0 in flight — 2026-08 spec absorbed on `main`.** The refreshed Fanar OpenAPI spec -(downloaded 2026-08-05; `openapi.json` normative + new `openapi.yaml` twin) is fully modelled: -`Fanar-Sadiq-2` + `persona` + `madhab`, streamed + emotional TTS, rich voice catalogue, image -prompt revision, the 499 `client_closed_request` error, envelope-code error routing, and Spring -AI vendor options. All shipping modules hold the 100 % JaCoCo gate. Pre-1.0; no Maven Central -artifacts yet (0.1.0 shipped 2026-04-28 as a GitHub Release). +**0.2.0 released 2026-08-06** ([v0.2.0](https://github.com/omahjoub/fanar-java/releases/tag/v0.2.0), +GitHub Release, 10 artifacts); `main` is at `0.3.0-SNAPSHOT`. The release delivers full parity +with the 2026-08 Fanar spec (`openapi.json` normative + `openapi.yaml` twin): `Fanar-Sadiq-2` + +`persona` + `madhab`, streamed + emotional TTS, rich voice catalogue, image prompt revision, +the 499 `client_closed_request` error, envelope-code error routing, and Spring AI vendor +options — three documented breaking changes under ADR-019. All shipping modules hold the +100 % JaCoCo gate. Pre-1.0; no Maven Central artifacts yet. Release process: +[docs/RELEASING.md](RELEASING.md). ## Shipped @@ -28,7 +30,6 @@ artifacts yet (0.1.0 shipped 2026-04-28 as a GitHub Release). ## Planned -- **0.2.0 release** — Pattern B release-and-bump flow once the spec-parity PRs land on `main`. - **Maven Central publication** — Sonatype account, GPG signing, release workflow, version-bump policy. (Intro email to the Fanar team sent 2026-05-01; awaiting Sonatype-path pointer.) - **Spring Boot 3 starter** — `fanar-spring-boot-3-starter` with the Jackson 2 codec; mechanical port of the SB4 starter. - **LangChain4j adapter** — `fanar-langchain4j` exposing the equivalent of Spring AI's adapters against LangChain4j's `ChatLanguageModel`. diff --git a/docs/RELEASING.md b/docs/RELEASING.md index 5f34f56..528bcb9 100644 --- a/docs/RELEASING.md +++ b/docs/RELEASING.md @@ -115,7 +115,9 @@ git push -u origin bump/$NEXT ### 7 — Post-release - [ ] Update `docs/PROJECT_STATE.md` (move the release from *Planned*, refresh the snapshot - date) — can ride in the bump-back PR. + date and phase) — can ride in the bump-back PR. +- [ ] Bump the README quick-start version snippets to `$NEXT` (they track `main`'s snapshot + version; they went stale after both 0.1.0 and 0.2.0 — hence this line). - [ ] Delete the `release/$VERSION` branch (the tag preserves the commit). - [ ] Optional smoke: clone at the tag and `./mvnw install`, or resolve an attached jar into a scratch project.