Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 11 additions & 3 deletions source/specifications/simple-repository-api.rst
Original file line number Diff line number Diff line change
Expand Up @@ -101,6 +101,10 @@ In addition to the above, the following constraints are placed on the API:
the file's provenance can be found at that URL. This URL **MUST** represent
a `secure origin <https://www.chromium.org/Home/chromium-security/prefer-secure-origins-for-powerful-new-features/>`_.

.. note::

The ``data-provenance`` attribute was added with API version 1.3.

.. note::

The format of the linked provenance is defined in :ref:`index-hosted-attestations`.
Expand Down Expand Up @@ -213,7 +217,7 @@ specification <version-specifiers>`.

This would end up looking like::

<meta name="pypi:repository-version" content="1.0">
<meta name="pypi:repository-version" content="1.3">

When interpreting the repository version:

Expand Down Expand Up @@ -405,7 +409,7 @@ As an example:

{
"meta": {
"api-version": "1.0"
"api-version": "1.3"
},
"projects": [
{"name": "Frob"},
Expand Down Expand Up @@ -509,13 +513,17 @@ Each individual file dictionary has the following keys:
associated provenance, with the same rules as ``data-provenance`` in the
:ref:`base HTML API specification <simple-repository-api-base>`.

.. note::

The ``provenance`` field was added with API version 1.3.

As an example:

.. code-block:: json

{
"meta": {
"api-version": "1.0"
"api-version": "1.3"
},
"name": "holygrail",
"files": [
Expand Down