Sergey KozyrenkoandClaude Opus 4.8 f3311ecadf ci: scope the codegen-freshness check to its inputs and name the fix ...

The check ran on every push and failed with a bare diff, so a backend schema
change surfaced as an unexplained red frontend job.

Run it only when a codegen input moved — the backend schema, the operations
document, the codegen config, or the lockfile (a codegen bump can change the
output, and skipping it there would let types.ts go stale and fail someone
else's later push). When the compare range can't be resolved (new branch,
force-push, tag) it still runs. On failure it now says which command to run.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-22 12:59:14 +07:00

..

ISSUE_TEMPLATE

repo final state

2026-03-26 06:16:07 +03:00

workflows

ci: scope the codegen-freshness check to its inputs and name the fix

2026-07-22 12:59:14 +07:00

PULL_REQUEST_TEMPLATE.md

fix: migration to pnpm

2026-04-21 01:59:08 +07:00

SAVED_REPLIES.md

repo final state

2026-03-26 06:16:07 +03:00