release: prep 0.3.1 patch (documentation-only fix for cost-per-token examples)#31
Merged
Conversation
…mples PR #30 just landed the 10x microcents fix on main. This bumps to 0.3.1 so the corrected javadoc + README examples ship on Maven Central. The 0.3.0 source/javadoc jars on Central carry the wrong numbers — anyone reading the javadoc from their IDE or from search.maven.org gets the incorrect example. A patch release is the only way to fix that surface. Standard release-prep delta .mvn/maven.config: -Drevision=0.3.0 -> 0.3.1 cycles-spring-ai-starter/pom.xml: <revision>0.3.0 -> 0.3.1 cycles-spring-ai-demo/pom.xml: <revision>0.3.0 -> 0.3.1 README.md dep snippet: <version>0.3.0 -> 0.3.1 CHANGELOG.md: new [0.3.1] section above [0.3.0] (no [Unreleased] block since main was clean after 0.3.0 plus the docs fix that motivated this patch) AUDIT.md change log: new "0.3.1 - 2026-05-12" entry above the 0.3.0 entry, noting "No public-API or property-key changes vs 0.3.0" What 0.3.1 ships vs 0.3.0 Strictly documentation. No source code in cycles-spring-ai-starter was modified between 0.3.0 and 0.3.1 (the merged PR #30 changed javadoc text on CyclesSpringAiProperties and a comment inside a test class - no behavior delta). The bundled jar's bytecode is byte-for-byte equivalent to 0.3.0 for behavior; the source/javadoc jars differ in javadoc text only. User-facing impact Anyone on 0.3.0 who set cycles.spring-ai.input-cost-per-token=25 (or =100 for output) from copying the wrong example was under-counting their actual provider cost by 10x. Real gpt-4o values in USD_MICROCENTS (per the Unit.java definition: 1 USD = 100,000,000 microcents) are: - input: $2.50/1M * 100M microcents/USD = 250 microcents/token - output: $10.00/1M * 100M microcents/USD = 1000 microcents/token Upgrade to 0.3.1 and bump the rate values by 10x. The 0.3.1 release notes (and the CHANGELOG entry) call this out explicitly so anyone reading the release page sees the issue immediately. Verification mvn -B clean verify -> BUILD SUCCESS, 152 tests, jacoco 100% / 100% mvn -B javadoc:jar -> zero warnings mvn -B help:evaluate -Dexpression=project.version -q -DforceStdout -> 0.3.1
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
1 participant
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.
Summary
Patch release shipping the corrected
inputCostPerToken/outputCostPerTokenjavadoc + README examples that landed onmainvia PR #30. The wrong examples are baked into 0.3.0's source/javadoc jars on Maven Central — a patch release is the only way to fix that surface for users reading docs from their IDE or search.maven.org.Standard release-prep delta
.mvn/maven.config-Drevision=0.3.0→-Drevision=0.3.1cycles-spring-ai-starter/pom.xml<revision>default →0.3.1cycles-spring-ai-demo/pom.xml<revision>default →0.3.1README.mddep snippet<version>0.3.0</version>→<version>0.3.1</version>CHANGELOG.md[0.3.1] — 2026-05-12section above[0.3.0]AUDIT.mdchange log0.3.1 — 2026-05-12entry, noting "No public-API or property-key changes vs 0.3.0"What 0.3.1 ships vs 0.3.0
Strictly documentation. Between 0.3.0 and 0.3.1:
CyclesSpringAiProperties.java— javadoc text only (no@Bean/@ConfigurationProperties/ field changes).CyclesBudgetAdvisorTest.java— one Java comment.README.md— two table cells + one YAML example block.The bundled jar's bytecode is byte-for-byte equivalent to 0.3.0 for behavior. The source/javadoc jars differ in javadoc text only.
User-facing impact
Anyone on 0.3.0 who set
cycles.spring-ai.input-cost-per-token=25(or=100for output) from copying the wrong example was under-counting actual provider cost by 10x. Real gpt-4o values in USD_MICROCENTS (perUnit.java's1 USD = 100,000,000 microcentsdefinition):$2.50/1M × 100M microcents/USD = 250 microcents/token$10.00/1M × 100M microcents/USD = 1000 microcents/tokenThe CHANGELOG entry calls this out explicitly so anyone reading the release page sees the issue immediately.
Verification
mvn -B clean verify→ BUILD SUCCESS, 152 tests, jacoco 100% / 100%mvn -B javadoc:jar→ zero warningsmvn -B help:evaluate -Dexpression=project.version -q -DforceStdout→0.3.1After this merges
→ publish workflow → Sonatype Central → Maven Central (~10–30 min propagation to repo1).
Test plan
0.3.1