chore(main): release 1.23.1

[openfeaturebot]

🤖 I have created a release beep boop

1.23.1 (2026-10-03)

🧹 Chore

• deps: update dependency com.diffplug.spotless:spotless-maven-plugin to v3.10.3 (#2050) (4728692)
• deps: update dependency com.google.guava:guava to v33.7.2-jre (#2055) (374f3a7)
• deps: update dependency com.tngtech.archunit:archunit-junit5 to v1.5.1 (#2047) (dc5419e)
• deps: update dependency io.cucumber:cucumber-bom to v7.34.9 (#2048) (bc35a66)
• deps: update dependency maven to v3.10.0 (#2054) (f55e0fd)
• deps: update dependency org.mockito:mockito-core to v5.24.0 (#2052) (f93b3eb)
• deps: update dependency org.slf4j:slf4j-api to v2.0.20 (#2049) (6fc08a2)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 463d14f4-4ad1-45a2-a30f-479e634c9beb

📥 Commits

Reviewing files that changed from the base of the PR and between ad156ed and ce517ca.

📒 Files selected for processing (1)

• CHANGELOG.md

🚧 Files skipped from review as they are similar to previous changes (1)

• CHANGELOG.md

Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review.

---

📝 Walkthrough

Walkthrough

The Java SDK release version changes from 1.23.0 to 1.23.1. Project metadata, the changelog, and README version references reflect the new version. The changelog lists five dependency updates.

Changes

Java SDK 1.23.1 release update

Layer / File(s)	Summary
Update project version metadata .release-please-manifest.json, pom.xml, version.txt	The release manifest, Maven project version, and version file change to 1.23.1.
Update release notes and README references CHANGELOG.md, README.md	The changelog records the 1.23.1 release and updates to ArchUnit JUnit 5 to 1.5.1, Cucumber BOM to 7.34.9, Maven to 3.10.0, Mockito Core to 5.24.0, and SLF4J API to 2.0.20. The README release badge and Maven and Gradle dependency examples reference 1.23.1.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Suggested reviewers: toddbaert

Merge Risk: ⚪ Minimal · up to ce517

This is a routine release notes update for version 1.23.1 and carries no evident merge risk.

Architecture Summary

Architecture risk: 🔵 Low · up to bb6eb

The change affects 4 systems.

Changed systems: CHANGELOG.md, pom.xml, README.md, version.txt

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — CHANGELOG.md (service) was modified; 1 changed file maps to changed impact.
• observed — pom.xml (service) was modified; 1 changed file maps to changed impact.
• observed — README.md (service) was modified; 1 changed file maps to changed impact.
• observed — version.txt (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in CHANGELOG.md: Adds the 1.23.1 changelog entry and a chore note documenting the ArchUnit JUnit 5 dependency update to v1.5.1.
• observed — Modified behavior in README.md: The release badge link and displayed version changed from 1.23.0 to 1.23.1.
• observed — Modified behavior in README.md: The Maven dependency example now specifies version 1.23.1 instead of 1.23.0.
• observed — Modified behavior in README.md: The Gradle dependency example now specifies version 1.23.1 instead of 1.23.0.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly identifies this as a release of version 1.23.1.
Description check	✅ Passed	The description summarizes the 1.23.1 release and lists dependency updates that relate to the changeset.

---

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.42%. Comparing base (4728692) to head (3509398).

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #2051      +/-   ##
============================================
+ Coverage     92.87%   93.42%   +0.55%     
- Complexity      752      754       +2     
============================================
  Files            62       62              
  Lines          1810     1810              
  Branches        208      208              
============================================
+ Hits           1681     1691      +10     
+ Misses           77       69       -8     
+ Partials         52       50       -2     

Flag	Coverage Δ
unittests	93.42% <ø> (+0.55%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud