Skip to content

Conversation

@openfeaturebot
Copy link
Contributor

@openfeaturebot openfeaturebot commented Dec 8, 2025

🤖 I have created a release beep boop

1.19.2 (2025-12-08)

🐛 Bug Fixes

  • context serialization missing props (with revert) (#1768) (4cb39a4)
  • context serialization with revert (4cb39a4)

🧹 Chore

  • deps: update com.vmlens.version to v1.2.23 (#1766) (04feac8)

This PR was generated with Release Please. See documentation.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @openfeaturebot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request is an automated release for version 1.19.2 of the OpenFeature Java SDK. Its primary purpose is to roll out a minor version bump that includes an update to the com.vmlens.version dependency. The changes encompass updates to version manifests, documentation, and build configuration files to ensure consistency across the project.

Highlights

  • New Release Version: The pull request introduces version 1.19.2 of the open-feature/java-sdk.
  • Dependency Update: The com.vmlens.version dependency has been updated to v1.2.23.
  • Automated Versioning: Various project files, including the changelog, README, and build configuration, have been automatically updated to reflect the new version number.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request, generated by Release Please, prepares for the 1.19.2 release. The main change included in this release is the update of the com.vmlens.version dependency to v1.2.23. The changes within this PR are limited to version bumps across various project files like pom.xml, README.md, and the CHANGELOG.md. I've reviewed the changes and they are all correct and consistent with an automated release process. The PR is good to merge.

@codecov
Copy link

codecov bot commented Dec 8, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.66%. Comparing base (4cb39a4) to head (7d1316f).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main    #1767      +/-   ##
============================================
+ Coverage     92.53%   93.66%   +1.13%     
- Complexity      599      602       +3     
============================================
  Files            55       55              
  Lines          1406     1406              
  Branches        154      154              
============================================
+ Hits           1301     1317      +16     
+ Misses           64       50      -14     
+ Partials         41       39       -2     
Flag Coverage Δ
unittests 93.66% <ø> (+1.13%) ⬆️

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

☔ View full report in Codecov by Sentry.
📢 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.

Signed-off-by: OpenFeature Bot <109696520+openfeaturebot@users.noreply.github.com>
@openfeaturebot openfeaturebot force-pushed the release-please--branches--main--components--dev.openfeature.sdk branch from 7d341eb to 7d1316f Compare December 8, 2025 22:59
@sonarqubecloud
Copy link

sonarqubecloud bot commented Dec 8, 2025

Copy link
Member

@toddbaert toddbaert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving and releasing this; it's a serious bug.

@toddbaert toddbaert merged commit c202935 into main Dec 8, 2025
11 of 14 checks passed
@toddbaert toddbaert deleted the release-please--branches--main--components--dev.openfeature.sdk branch December 8, 2025 23:04
@openfeaturebot
Copy link
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants