fix: fail builds after generation errors - #3195
Open
OskarEichler wants to merge 1 commit into
Open
Conversation
This was referenced Sep 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Problem
The build entrypoint catches generation failures and logs them, but then exits successfully. CI or release automation can therefore treat an incomplete build as valid.
Breaking changes
Build commands that encounter a generation error now exit unsuccessfully instead of returning status 0. Runtime APIs and generated package behavior are unchanged.
Verification
devand passes with this changenpm test: 94 suites, 795 tests passednpm run lintNODE_OPTIONS=--openssl-legacy-provider npm run buildgit diff --check