Repository navigation
fix(data_connect): exclude generated protobuf sources from analysis - #18687
Conversation
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 the 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 counterproductive. 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. |
3 participants
Description
protobuf6.1.0 (published 2026-09-11) deprecatedcreatein favour of theStruct()/ListValue()/Duration()constructors.firebase_data_connectdepends on
protobuf: ^6.0.0, so CI resolves 6.1.0 and the checked-in generated.pb.dartsources emit 7deprecated_member_useinfos.dart analyze --fatal-infosturns those into a hard failure, so theanalyzejob is red onevery PR opened since 2026-09-11.
Generated protobuf sources aren't hand-maintained, so they're now excluded from
analysis — matching what the sibling
examplepackage already does forlib/generated/**, and what theformatjob already does via--ignore "**/generated/**".Breaking Change