Repository navigation
Diagnose fixed frontend release constraints without values - #740
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
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.
The fixed frontend publisher stops before upload, while the existing schema projection only reports types. Add bounded boolean diagnostics for each relevant configuration constraint so the read-only preflight can identify the rejecting condition without exposing binding identities, values, or provider error bodies.
The publish, activation, rollback, permissions and default paths are unchanged. Targeted safety validation and actionlint pass; synthetic cases cover format, identity, duplicate, secret-shape and unknown-field failures. This does not declare the live release error fixed.