Repository navigation
Validate named exports in fixed frontend release comparison - #739
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.
Accept the documented
resources.script.named_handlersfield when checking retained Worker configuration. Validate bounded named-export identities and handler arrays, reject malformed/duplicate entries, and compare the field between old and new versions before activation. Other unknown fields still fail closed.The read-only diagnostic recognizes the field by type without emitting its contents. Worker code, bindings, pins and runtime configuration are unchanged.
Validation: native deployment-safety tests (60 release-flow cases and 8 diagnostic cases), actionlint, and independent scoped ABI/privacy review passed. The earlier live release stopped before upload or activation; this PR does not claim a live deployment has passed.