[Reputation Oracle] Use manifest encryption state for final results#3898
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 5 Skipped Deployments
|
portuu3
approved these changes
May 19, 2026
github-project-automation
Bot
moved this from In Review
to Done
in Core tech - 2026 (H1)
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
2 participants
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.
Issue tracking
Freestyle
Context behind the change
Final results were always encrypted during escrow completion. This could block completion when the required PGP public keys were missing. The agreed behavior is to follow the manifest encryption state instead:
This keeps result handling consistent with how the job launcher created the escrow manifest.
How has this been tested?
TBT
Release plan
None
Potential risks; What to monitor; Rollback plan
None