Require acceptance audience and return failure exit codes - #1
Merged
Merged
Conversation
schchit
marked this pull request as ready for review
September 13, 2026 02:35
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.
Require acceptance audience and return failure exit codes.
jep verify --mode acceptancerequires--expected-audience. The value is forwarded to the API and negative verification exits with status 2. Malformed input/transport errors exit with status 1.--refaccepts either a digest or a JSON reference descriptor. All verification assurance comes from the configured API; the CLI does not perform local cryptographic verification.Verification for this revision
9 Python regression tests passed.
The companion cross-repository harness passed all 12 SDK J/D/T/V checks, 8 Python/TypeScript reference-validator checks, the packaged Action API path, and API restart/replay persistence. No merge or package publication is included.