Skip to content

Commit

Permalink
PEP 740: clarify that provenance is nullable (#3906)
Browse files Browse the repository at this point in the history
Signed-off-by: William Woodruff <[email protected]>
  • Loading branch information
woodruffw authored Aug 22, 2024
1 parent 5ab4c64 commit 7fbacdc
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions peps/pep-0740.rst
Original file line number Diff line number Diff line change
Expand Up @@ -235,9 +235,9 @@ The following changes are made to the
* When an uploaded file has one or more attestations, the index **MAY**
include a ``provenance`` key in the ``file`` dictionary for that file.

The value of the ``provenance`` key **SHALL** be a JSON string, which
**SHALL** be the SHA-256 digest of the associated ``.provenance`` file,
as in the Simple Index.
The value of the ``provenance`` key **SHALL** be either a JSON string
or ``null``. If ``provenance`` is not ``null``, it **SHALL** be the SHA-256
digest of the associated ``.provenance`` file, as in the Simple Index.

See :ref:`appendix-3` for an explanation of the technical decision to
embed the SHA-256 digest in the JSON API, rather than the full
Expand Down

0 comments on commit 7fbacdc

Please sign in to comment.