Skip to content

v17.0.0

Latest

Choose a tag to compare

@OTA-Release-Bot OTA-Release-Bot released this 14 Oct 09:15

17.0.0 - 2026-10-14

Development of this release was supported by the NGI0 Commons Fund, a fund established by NLnet with financial support from the European Commission's Next Generation Internet programme, under the aegis of DG CNECT under grant agreement N°101069594.

Changed

  • Use the OTA_ENGINE_GITHUB_TOKEN environment variable only to publish datasets, as the engine no longer needs it to track terms
  • Publish datasets to GitLab when the OTA_ENGINE_GITLAB_RELEASES_TOKEN environment variable is defined, as it is the token that authenticates the publishing requests; the OTA_ENGINE_GITLAB_TOKEN environment variable is no longer used and can be removed

Removed

  • Breaking: Remove the reporter that created issues on GitHub or GitLab when tracking failed, along with its reporter configuration; install the @opentermsarchive/issue-reporter module in the collection, move the reporter configuration to its @opentermsarchive/issue-reporter key with an additional collectionApi.url entry, replacing any legacy githubIssues entry with "type": "github" next to the same repositories, rename the token environment variable to OTA_ISSUE_REPORTER_GITHUB_TOKEN or OTA_ISSUE_REPORTER_GITLAB_TOKEN, and run ota-issue-reporter sync --schedule alongside the engine, as described in how to report tracking failures
  • Breaking: Remove the scripts/reporter/duplicate script, which closed the duplicate issues that engines older than v2.3.2 could create

Fixed

  • Publish datasets to GitLab through the proxy defined by the lowercase http_proxy or https_proxy environment variables, or by HTTP_PROXY alone, as the fetching of terms already does