Repository navigation
docs: document output.file.sha256 on job output files - #109
Merged
Merged
Conversation
Every file example now shows the field: a real digest on single-file outputs and null on the files of a multi-file output. The Job page says what it is and when it is null, and the ffmpeg page says how to verify a download with it.
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 API now returns
sha256on every output file (live on prod since 2026-10-10).nullon the files of a multi-file output.concepts/jobexplains the field and when it isnull.jobs/ffmpegexplains how to verify a download or a delivered copy with it.Checked against prod: an ffmpeg job and an image job both returned a value equal to a local digest of the download.