Ocdskit

Latest version: v1.3.2

Safety actively analyzes 723217 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 9 of 10

0.1.4

------------------

Added
~~~~~

New CLI options:

- :ref:`combine-record-packages`: ``--fake``
- :ref:`combine-release-packages`: ``--fake``
- :ref:`compile`: ``--fake``
- :ref:`package-records`: ``--fake``
- :ref:`package-releases`: ``--fake``

New CLI commands:

- :ref:`package-records`

New library methods:

- :func:`ocdskit.combine.package_records`

Changed
~~~~~~~

- :ref:`mapping-sheet`: Improve documentation of ``--extension`` and ``--extension-field``.

Fixed
~~~~~

- :ref:`detect-format` correctly detects concatenated JSON, even if subsequent JSON values are non-OCDS values.

0.1.3

------------------

Changed
~~~~~~~

- Set missing package metadata to ``""`` instead of ``null`` in CLI commands, to mirror library methods.

0.1.2

------------------

Changed
~~~~~~~

- Align the library methods :func:`ocdskit.util.json_dump` and :func:`ocdskit.util.json_dumps`.

0.1.1

------------------

Fixed
~~~~~

- :ref:`upgrade` no longer errors if specific fields are ``null``.
- :ref:`upgrade` no longer errors on packages that have ``parties`` values without ``id`` fields and that declare no version or a version of "1.0".

0.1.0

------------------

Command-line inputs can now be `concatenated JSON <https://en.wikipedia.org/wiki/JSON_streaming#Concatenated_JSON>`__ or JSON arrays, not only `line-delimited JSON <https://en.wikipedia.org/wiki/JSON_streaming#Line-delimited_JSON>`__.

Added
~~~~~

New CLI commands:

- :ref:`detect-format`

New CLI options:

- :ref:`package-releases`:

- ``--uri``
- ``--published-date``
- ``--publisher-name``
- ``--publisher-uri``
- ``--publisher-scheme``
- ``--publisher-uid``

- :ref:`compile`:

- ``--publisher-name``
- ``--publisher-uri``
- ``--publisher-scheme``
- ``--publisher-uid``

- :ref:`combine-record-packages`:

- ``--publisher-name``
- ``--publisher-uri``
- ``--publisher-scheme``
- ``--publisher-uid``

- :ref:`combine-release-packages`:

- ``--publisher-name``
- ``--publisher-uri``
- ``--publisher-scheme``
- ``--publisher-uid``

- :ref:`mapping-sheet`:

- ``--order-by``
- ``--infer-required``
- ``--extension``
- ``--extension-field``

The ``--root-path`` option is added to all OCDS commands.

New library methods:

- :func:`ocdskit.combine.package_releases`
- :func:`ocdskit.combine.combine_record_packages`
- :func:`ocdskit.combine.combine_release_packages`
- :func:`ocdskit.combine.compile_release_packages`
- :func:`ocdskit.mapping_sheet.mapping_sheet`
- :func:`ocdskit.schema.get_schema_fields`

Changed
~~~~~~~

- **Backwards-incompatible**: :func:`ocdskit.upgrade.upgrade_10_10`, :func:`ocdskit.upgrade.upgrade_11_11` and :func:`ocdskit.upgrade.upgrade_10_11` now return data, instead of only editing in-place.
- **Backwards-incompatible**: :ref:`mapping-sheet` and :ref:`schema-report` now read a file argument instead of standard input, to support schema that ``$ref`` other schema.
- :ref:`mapping-sheet` and :ref:`schema-report` support schema from: Open Contracting for Infrastructure Data Standard (OC4IDS), Beneficial Ownership Data Standard (BODS), and Social Investment Data Lab Specification (SEDL).
- :ref:`mapping-sheet` outputs:

- ``enum`` values of ``items``
- ``enum`` as "Enum:" instead of "Codelist:"
- ``pattern`` as "Pattern:"

- :ref:`schema-strict` adds ``"uniqueItems": true`` to all arrays, unless ``--no-unique-items`` is set.
- Use ``https://`` instead of ``http://`` for ``standard.open-contracting.org``.

Fixed
~~~~~

- :ref:`compile` merges extensions' schema into the release schema before merging releases.
- :ref:`mapping-sheet` fills in the deprecated column if an object field uses ``$ref``.
- :ref:`schema-strict` no longer errors if a required field uses ``$ref``.
- :ref:`upgrade` no longer errors if ``awards`` or ``contracts`` is ``null``.

0.0.5

------------------

Added
~~~~~

New CLI options:

- :ref:`compile`:

- ``--schema``: You can create compiled releases and versioned releases using a specific release schema.
- ``--linked-releases``: You can have the record package use linked releases instead of full releases.
- ``--uri``, ``--published-date``: You can set the ``uri`` and ``publishedDate`` of the record package.

- If not set, these will be ``null`` instead of the ``uri`` and ``publishedDate`` of the last package.

- :ref:`combine-record-packages`: ``--uri``, ``--published-date``
- :ref:`combine-release-packages`: ``--uri``, ``--published-date``

New CLI commands:

- :ref:`upgrade`

Changed
~~~~~~~

- :ref:`compile` raises an error if the release packages use different versions.
- :ref:`compile` determines the version of the release schema to use if ``--schema`` isn't set.
- :ref:`compile`, :ref:`combine-release-packages` and :ref:`combine-record-packages` have a predictable field order.
- ``measure`` is removed.

Fixed
~~~~~

- :ref:`indent` prints an error if a path doesn't exist.
- :ref:`compile`, :ref:`combine-release-packages` and :ref:`combine-record-packages` succeed if the required ``publisher`` field is missing.

Page 9 of 10

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.