Skip to content

v16.1.0

Choose a tag to compare

View all tags
@OTA-Release-Bot OTA-Release-Bot released this 23 Sep 15:02
· 60 commits to main since this release
v16.1.0
fa23c39

16.1.0 - 2026-09-23

Development of this release was supported by User Rights and 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.

Added

  • Add a tracking-results data repository recording the tracking status of each terms and the lifecycle of every run in a tamper-evident Git history (RFC)
  • Add @opentermsarchive/engine.tracking-results configuration defining the storage location, author and publication of the tracking-results repository; defaults record locally to ./data/tracking-results without publication; set it to null to disable tracking-results
  • Add an x-run-id metadata to snapshots and versions recorded while a tracking-results run is in progress, tying each record to the run that produced it; it is a commit trailer with Git storage
  • Reject in ota validate the service IDs containing characters that cannot be used in file names on every supported platform (/, \, :, ", <, >, |, *, ?, control characters), as documented in the service ID guidelines

Changed

  • Mention the declared URL instead of the last redirect target in the errors of fetches that fail because of redirects, so that the error stays the same from one tracking to the next

Fixed

  • Record as a technical upgrade the version of combined terms whose newly declared source document could only be fetched on a retry, instead of refetching all their source documents and recording a regular change that notified a false modification of the terms
  • Stop stating in tracking issues that the source documents were recorded as snapshots and that missed versions may be recovered, when they could actually not be fetched
  • Fix the links to the latest snapshots in the tracking issues of combined terms, which pointed to a nonexistent file with a .null extension for every source document that was successfully fetched; also omit these links for source documents that have never been recorded as snapshots, as there is no file to link to
  • Pass falsy parameters, such as false or 0, to collection-specific filters, which received the extraction context in their place
  • Track only once a service whose ID is given several times to ota track --services
Assets 2
Loading