feat(infra/prod): onboard 25 repositories to automation for publish-release#2907
feat(infra/prod): onboard 25 repositories to automation for publish-release#2907
Conversation
Summary of ChangesHello @ohmayr, 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 significantly expands the scope of Librarian automation by integrating 32 additional Python repositories. The primary goal is to enable automated Highlights
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request onboards 32 new Python repositories for publish-release automation and also sorts all repository entries alphabetically, which improves maintainability. The changes look good. I have one suggestion to further improve the configuration file by removing redundant full-name fields, taking advantage of the default URL generation logic in the application.
a64d088 to
8fb11c5
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2907 +/- ##
=======================================
Coverage 83.32% 83.32%
=======================================
Files 133 133
Lines 10926 10926
=======================================
Hits 9104 9104
Misses 1409 1409
Partials 413 413 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@ohmayr can you confirm all these repositories are already onboarded to Librarian? ex: they have a state.yaml file and are using Librarian to release? |
8fb11c5 to
9e55bba
Compare
PR created by the Librarian CLI to initialize a release. Merging this PR will auto trigger a release. Librarian Version: not available Language Image: us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/librarian-release-container:latest <details><summary>librarian: 0.7.0</summary> ## [0.7.0](v0.6.0...v0.7.0) (2025-11-20) ### Features * add command execution package with logging (#2968) ([12f4e94](12f4e949)) * add branch support to RepositoryConfig (#2906) ([2cab5d6](2cab5d65)) * add image sha as a config in repositories config (#2954) ([3d1f537](3d1f5375)) * add initial config (#2965) ([502b063](502b063c)) * add fetch package (#2964) ([53de44d](53de44d8)) * parse gapic_metadata for API version release notes (#2815) ([7ee0328](7ee03283)) * onboard 25 repositories to automation for publish-release (#2907) ([87fae04](87fae04a)) * add version command (#2894) ([8f85be0](8f85be09)) * add RequireCommand test helper (#2978) ([a820a71](a820a710)) * add initial command (#2961) ([c959aea](c959aeae)) * add `stage-release` command (#2902) ([ee05006](ee050065)) ### Bug Fixes * require git v2.28.0 (#2963) ([265ee47](265ee47f)) * enums referenced outside the package (#2952) ([7331816](73318169)) </details>
This PR onboards all the remaining Python repositories for Librarian automation to support the
publish-releasecommand.We'll determine which repos require support for
generateand/orstage-releaseand will address that separately.