Skip to content

feat(internal/librarian): find release commits and libraries released#3642

Merged
jskeet merged 1 commit intogoogleapis:mainfrom
jskeet:find-release-changes
Jan 20, 2026
Merged

feat(internal/librarian): find release commits and libraries released#3642
jskeet merged 1 commit intogoogleapis:mainfrom
jskeet:find-release-changes

Conversation

@jskeet
Copy link
Copy Markdown
Contributor

@jskeet jskeet commented Jan 20, 2026

Add findReleasedLibraries, which determines which libraries are released by a specific commit.

Add findLatestReleaseCommit, which looks back in git history to find the first commit to release either any library, or just a specified library.

These will be used by the tag and publish commands.

Fixes #3597

@jskeet jskeet requested a review from a team as a code owner January 20, 2026 12:13
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @jskeet, 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 enhances the librarian tool by adding robust capabilities to detect and track library releases within a Git repository. It provides mechanisms to programmatically determine which libraries have undergone a version change between two points in time and to find the exact commit where such a release was made. This foundational work is critical for automating and improving the accuracy of future tag and publish operations, ensuring consistent and reliable release management.

Highlights

  • New Functionality: Library Release Detection: Introduced findReleasedLibraries to identify which libraries have been released based on changes between two configuration states. This function validates SemVer compliance, ensuring no version regressions occur.
  • New Functionality: Latest Release Commit Identification: Added findLatestReleaseCommitHash to traverse Git history and pinpoint the most recent commit that corresponds to a library release, either for a specific library or any library.
  • Integration with Release Commands: These new functions are designed to be utilized by the tag and publish commands within the librarian tool, streamlining the release process.
  • Issue Resolution: This pull request addresses and fixes issue librarian: publish command: determine which libraries are released by a commit #3597.

🧠 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.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Warning

Gemini encountered an error creating the review. You can try again by commenting /gemini review.

@jskeet
Copy link
Copy Markdown
Contributor Author

jskeet commented Jan 20, 2026

/gemini review.

@codecov
Copy link
Copy Markdown

codecov bot commented Jan 20, 2026

Codecov Report

❌ Patch coverage is 95.45455% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 82.51%. Comparing base (bab9e00) to head (a81efc3).
⚠️ Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
internal/librarian/release.go 95.45% 1 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3642      +/-   ##
==========================================
+ Coverage   82.46%   82.51%   +0.04%     
==========================================
  Files         140      140              
  Lines       12669    12713      +44     
==========================================
+ Hits        10448    10490      +42     
- Misses       1731     1732       +1     
- Partials      490      491       +1     

☔ 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.

Copy link
Copy Markdown
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 introduces new functionality to identify released libraries and find the latest commit associated with a release. The new functions, findReleasedLibraries and findLatestReleaseCommitHash, are well-documented and come with comprehensive, table-driven tests that adhere to the project's testing guidelines. The logic for determining library releases and navigating git history appears sound and covers various edge cases. Overall, this is a solid addition to the codebase.

@jskeet jskeet force-pushed the find-release-changes branch 2 times, most recently from f7d125b to 863db48 Compare January 20, 2026 12:47
Add findReleasedLibraries, which determines which libraries are
released by a specific commit.

Add findLatestReleaseCommit, which looks back in git history to find
the first commit to release either any library, or just a specified
library.

These will be used by the tag and publish commands.

Fixes googleapis#3597
@jskeet jskeet force-pushed the find-release-changes branch from 863db48 to a81efc3 Compare January 20, 2026 14:17
@jskeet jskeet requested a review from julieqiu January 20, 2026 14:25
@jskeet jskeet merged commit 0159fc1 into googleapis:main Jan 20, 2026
11 checks passed
@jskeet jskeet deleted the find-release-changes branch January 20, 2026 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

librarian: publish command: determine which libraries are released by a commit

2 participants