Deploy nlohmann-json package to platform-independent package repository

[mgovers]

• We upload an nlohmann-json package to PyPI as an independent repackaging of the nlohmann-json package in HomeBrew our organization created in this repo.
  • For the time being, we own that repackaging software
  • We are, however, very happy to transfer ownership of this software and the nlohmann-json package in PyPI to the nlohmann organization
  • If you would like any help to find a more clean way to repackage or push to PyPI, we are very open to providing input.

Issue

Platform- and environment-independently downloading the latest release in automation software is flaky.

Background

In our workflow, we would like to build a Python wrapper around a C library. If possible, we would like to do so within the Python package builder without having to care about any C++ package manager. The user should be able to install the Wheel of the Python package while only depending on other Python packages.

In our ecosystem, we enable the above, by downloading the latest released version of the nlohmann-json package in automation and scripts via the GitHub API. However, the GitHub API has a rate limit that is very regularly exceeded, resulting in 403 errors (see for example this pipeline run). A workaround could be to use the direct HTTPS URL instead of the API, but that also has a rate limit, albeit a bit higher. It would be no more than a temporary fix.

Proposed solution

Push the nlohmann-json header-only package to multiple package managers for platform- and environment-independent usage.

Describe alternatives you have considered

• nlohmann-json package in HomeBrew is not platform independent
• nlohmann_json package in conda-forge may not be available everywhere by design (e.g.: when building Python bindings for non-conda environments)
• nlohmann-json package in PyPI is an independent repackaging of the nlohmann-json package in HomeBrew our organization created in this repo. See also the top of this discussion.
  • For the time being, we own that repackaging software
  • We are, however, very happy to transfer ownership of this software and the nlohmann-json package in PyPI to the nlohmann organization
  • If you would like any help to find a more clean way to repackage or push to PyPI, we are very open to providing input.