flyteorg/flyte

[Build] Make `make gen` more robust

Open

#6845 opened on Jan 5, 2026

View on GitHub
 (4 comments) (1 reaction) (2 assignees)Python (3,705 stars) (378 forks)batch import
flyte2good first issue

Description

make gen will cause multiple changes even if there's no update in protobuf, for example:

We should improve the make gen command to only generate things when there's update in protobuf

Tasks:

Contributor guide

Tech stack
pythonrustrest api
Domain
build systembackend
Issue type
chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
MakeProtobufRustPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Review the existing PRs #6844 and #6833 for preventing Cargo.lock and swagger.json changes. Analyze the Makefile's gen target and identify how protobuf updates trigger lock file changes. Then implement a similar check for uv.lock to ensure it only updates when protobuf changes, and test by making a protobuf change and running make gen.