Skip to content

Conversation

@Hmnt39
Copy link
Contributor

@Hmnt39 Hmnt39 commented Dec 22, 2025

This PR releases a new version for the python-extractor-utils.

@Hmnt39 Hmnt39 requested a review from a team as a code owner December 22, 2025 05:47
@gemini-code-assist
Copy link

Summary of Changes

Hello @Hmnt39, 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 formally releases version "7.11.2" of the python-extractor-utils library. The primary purpose of this release is to address a critical bug concerning metrics handling within the unstable package, ensuring more robust and independent metrics management by individual extractors.

Highlights

  • Version Update: The project version has been updated from "7.11.1" to "7.11.2" across relevant configuration and source files.
  • Metrics Pickling Fix: A bug related to metrics pickling in the unstable package has been resolved, preventing the runtime from passing Metrics instances.
  • Extractor Metrics Management: Extractors are now responsible for creating and managing their own Metrics instances, improving stability and control.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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

@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 for the release of version 7.11.2. The changes correctly update the version number in pyproject.toml, cognite/extractorutils/__init__.py, and add a corresponding entry to CHANGELOG.md. The version bump to a patch release is appropriate for the bug fix described. The changes are consistent and look good for the release.

@codecov
Copy link

codecov bot commented Dec 22, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.04%. Comparing base (8537632) to head (7269302).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #499   +/-   ##
=======================================
  Coverage   81.04%   81.04%           
=======================================
  Files          43       43           
  Lines        4210     4210           
=======================================
  Hits         3412     3412           
  Misses        798      798           
Files with missing lines Coverage Δ
cognite/extractorutils/__init__.py 100.00% <100.00%> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Hmnt39 Hmnt39 added the waiting-for-risk-review Waiting for a member of the risk review team to take an action label Dec 22, 2025
@haakonvt haakonvt self-assigned this Dec 23, 2025
@haakonvt haakonvt added the risk-review-ongoing Risk review is in progress label Dec 23, 2025
Copy link
Contributor

@haakonvt haakonvt left a comment

Choose a reason for hiding this comment

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

🦄

@haakonvt haakonvt added waiting-for-team Waiting for the submitter or reviewer of the PR to take an action and removed waiting-for-risk-review Waiting for a member of the risk review team to take an action labels Dec 23, 2025
@Hmnt39 Hmnt39 merged commit e6df6dc into master Dec 23, 2025
6 checks passed
@Hmnt39 Hmnt39 deleted the chore/release branch December 23, 2025 08:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk-review-ongoing Risk review is in progress waiting-for-team Waiting for the submitter or reviewer of the PR to take an action

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants