Skip to content

chore(main): release dev.openfeature.contrib.providers.flipt 0.1.4#1706

Open
openfeaturebot wants to merge 1 commit intomainfrom
release-please--branches--main--components--dev.openfeature.contrib.providers.flipt
Open

chore(main): release dev.openfeature.contrib.providers.flipt 0.1.4#1706
openfeaturebot wants to merge 1 commit intomainfrom
release-please--branches--main--components--dev.openfeature.contrib.providers.flipt

Conversation

@openfeaturebot
Copy link
Contributor

🤖 I have created a release beep boop

0.1.4 (2026-03-02)

🐛 Bug Fixes

  • security: update dependency com.fasterxml.jackson.core:jackson-core to v2.21.1 [security] (#1705) (7760d09)

This PR was generated with Release Please. See documentation.

Signed-off-by: OpenFeature Bot <109696520+openfeaturebot@users.noreply.github.com>
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, 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 automates the release of version 0.1.4 for the dev.openfeature.contrib.providers.flipt module. The primary purpose of this release is to incorporate a critical security update for the jackson-core dependency, ensuring the provider remains secure and up-to-date.

Highlights

  • New Release: The dev.openfeature.contrib.providers.flipt module has been released as version 0.1.4.
  • Security Update: This release includes a security fix, updating the com.fasterxml.jackson.core:jackson-core dependency to v2.21.1.
Changelog
  • .release-please-manifest.json
    • Updated the version of the providers/flipt module to 0.1.4.
  • providers/flipt/CHANGELOG.md
    • Added a new changelog entry for version 0.1.4.
    • Documented a security bug fix for the jackson-core dependency.
  • providers/flipt/README.md
    • Updated the Maven dependency version in the installation instructions to 0.1.4.
  • providers/flipt/pom.xml
    • Incremented the project version to 0.1.4.
  • providers/flipt/version.txt
    • Updated the version string to 0.1.4.
Activity
  • This pull request was automatically generated by Release Please.
  • The release includes a bug fix for a security vulnerability related to the jackson-core dependency.
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 prepares the release of dev.openfeature.contrib.providers.flipt version 0.1.4. The main change in this version is a security fix related to the com.fasterxml.jackson.core:jackson-core dependency. However, my review identified a critical issue with how this fix was applied. The updated dependency is scoped for testing only, which means the published artifact will still use the vulnerable version. This needs to be corrected before merging.


### 🐛 Bug Fixes

* **security:** update dependency com.fasterxml.jackson.core:jackson-core to v2.21.1 [security] ([#1705](https://github.com/open-feature/java-sdk-contrib/issues/1705)) ([7760d09](https://github.com/open-feature/java-sdk-contrib/commit/7760d098b6c965c5a299e274ddf790e10b967738))
Copy link
Contributor

Choose a reason for hiding this comment

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

critical

The security fix mentioned in this changelog entry for com.fasterxml.jackson.core:jackson-core appears to be incorrectly implemented. In the providers/flipt/pom.xml file, the updated dependency is defined with <scope>test</scope>:

<dependency>
    <groupId>com.fasterxml.jackson.core</groupId>
    <artifactId>jackson-core</artifactId>
    <version>2.21.1</version>
    <scope>test</scope>
</dependency>

This configuration means the updated, secure version of jackson-core is only used during the test phase and is not included in the final artifact. The artifact will instead use the older, vulnerable version brought in as a transitive dependency from jackson-databind. To ensure the security fix is effective, the <scope>test</scope> should be removed from the jackson-core dependency declaration.

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