Skip to content

fix(legacylibrarian): restore chore as noop#5811

Merged
noahdietz merged 9 commits into
googleapis:mainfrom
noahdietz:legacylibrarian-chore-noop-release
May 6, 2026
Merged

fix(legacylibrarian): restore chore as noop#5811
noahdietz merged 9 commits into
googleapis:mainfrom
noahdietz:legacylibrarian-chore-noop-release

Conversation

@noahdietz
Copy link
Copy Markdown
Contributor

@noahdietz noahdietz commented May 4, 2026

Restores previous legacylibrarian behavior that would allow chore commits (which map to a semver.ChangeLevel of semver.None) through as "no-op" changes. After this, a library with only chore commits will not be considered eligible for release. More background/details in #5786.

Updates librarianops generate to produce a feat commit. Corresponding playbook updates will follow.

Fixes #5786

@noahdietz noahdietz requested a review from a team as a code owner May 4, 2026 23:17
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 refactors the versioning logic in NextVersion to prevent unnecessary minor version bumps in releaseOnlyMode when no releasable changes are present. Specifically, it adds a check for highestChange != semver.None and updates associated tests to reflect that chore commits no longer trigger bumps in this mode. Feedback suggests simplifying the logic by removing a redundant length check and restoring documentation for the non-obvious versioning behavior.

Comment thread internal/legacylibrarian/legacylibrarian/commit_version_analyzer.go Outdated
…er.go

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Noah Dietz <noahdietz@users.noreply.github.com>
sofisl
sofisl previously approved these changes May 5, 2026
@jskeet
Copy link
Copy Markdown
Contributor

jskeet commented May 5, 2026

Doesn't this mean that no librarian generation PRs will trigger a release? Or is the intention that Librarian PRs will now have a "feat" commit?

@noahdietz
Copy link
Copy Markdown
Contributor Author

Or is the intention that Librarian PRs will now have a "feat" commit?

@jskeet, this! See the Respect no-op, use minor section of the issue: #5786

@jskeet
Copy link
Copy Markdown
Contributor

jskeet commented May 5, 2026

Or is the intention that Librarian PRs will now have a "feat" commit?

@jskeet, this! See the Respect no-op, use minor section of the issue: #5786

Cool - sorry for missing that before :)

@noahdietz noahdietz requested review from jskeet and sofisl May 5, 2026 22:53
@noahdietz
Copy link
Copy Markdown
Contributor Author

Or is the intention that Librarian PRs will now have a "feat" commit?

@jskeet, this! See the Respect no-op, use minor section of the issue: #5786

Cool - sorry for missing that before :)

But now that you got me thinking about it, I also updated librarianops to produce a feat commit :)

@noahdietz noahdietz dismissed sofisl’s stale review May 6, 2026 16:50

Made changes, need re-review

@noahdietz noahdietz merged commit 9a6d972 into googleapis:main May 6, 2026
24 checks passed
@noahdietz noahdietz deleted the legacylibrarian-chore-noop-release branch May 6, 2026 16:57
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.

legacylibrarian: Consider restoring chore as a no-op commit when determining release eligibility

3 participants