Skip to content

chore(librarian): put repo into legacylibrarian release-only mode#16591

Open
jskeet wants to merge 1 commit intogoogleapis:mainfrom
jskeet:legacylibrarian-release-only-mode
Open

chore(librarian): put repo into legacylibrarian release-only mode#16591
jskeet wants to merge 1 commit intogoogleapis:mainfrom
jskeet:legacylibrarian-release-only-mode

Conversation

@jskeet
Copy link
Copy Markdown
Contributor

@jskeet jskeet commented Apr 9, 2026

Attempting to regenerate using legacylibrarian will fail, and releasing will not expect commits to be generated by legacylibrarian.

Attempting to regenerate using legacylibrarian will fail,
and releasing will not expect commits to be generated by
legacylibrarian.
@jskeet jskeet requested a review from daniel-sanche April 9, 2026 11:01
@jskeet jskeet requested review from a team as code owners April 9, 2026 11:01
@jskeet jskeet added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Apr 9, 2026
@jskeet
Copy link
Copy Markdown
Contributor Author

jskeet commented Apr 9, 2026

Note: this has the "do not merge" label so we can wait for a go/no-go decision before proceeding.

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 updates the .librarian/config.yaml file to enable release_only_mode. This change configures the repository for a specific legacylibrarian mode, indicating that regeneration using legacylibrarian will fail and releases will not expect legacylibrarian-generated commits, likely as part of a migration. There is no feedback to provide.

@parthea parthea changed the title chore: put repo into legacylibrarian release-only mode chore(librarian): put repo into legacylibrarian release-only mode Apr 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge Indicates a pull request not ready for merge, due to either quality or timing.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants