v0.34.1

0.34.1 - 2023-12-19

Full changeset and discussions: #1037.

Development of this release was made on a volunteer basis by @Ndpnt.

Fixed

• Improve performance for large-scale MongoDB databases

v0.34.0

0.34.0 - 2023-12-11

Full changeset and discussions: #1033.

Development of this release was supported by the NGI0 Entrust 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

• Expose versions data through the collection API (#1003). When using Git as storage for versions, this API relies on the assumption that the commit date matches the author date, introduced in the engine in June 2022 (#875). If your collection was created before this date, inconsistencies in the API results may arise. You can verify if your version history includes commits with commit dates differing from author dates by executing the following command at the root of your versions repository: git log --format="%H %ad %cI" --date=iso-strict | awk '{if ($2 != $3) print "Author date", $2, "and commit date", $3, "mismatch for commit", $1 }'. You can correct the history with the command: git rebase --committer-date-is-author-date $(git rev-list --max-parents=0 HEAD). Since the entire history will be rewritten, a force push may be required for distributed repositories

Changed

• Provide a succinct JSON-formatted error message as response in API errors

v0.33.1

0.33.1 - 2023-11-28

Full changeset and discussions: #1032.

Development of this release was supported by the French Ministry for Foreign Affairs through its ministerial State Startups incubator under the aegis of the Ambassador for Digital Affairs.

Fixed

• Update ESLint to use the stylistic plugin following deprecation of formatting rules, correcting a randomly-appearing Configuration for rule "lines-between-class-members" is invalid error

v0.33.0

0.33.0 - 2023-11-27

Full changeset and discussions: #1031.

Development of this release was supported by the NGI0 Entrust 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 terms attribute to /services API response, containing declared term types for each service

v0.32.1

0.32.1 - 2023-10-18

Full changeset and discussions: #1026.

Added

• Ensure Reporter configuration is defined before instantiating it
• Ensure to add links to versions and snapshots in issues only if repositories are defined in configuration

Removed

• No longer define default configuration for Reporter module

v0.32.0

0.32.0 - 2023-10-18

Full changeset and discussions: #1025.

Added

• Auto create labels for declarations repository on GitHub
• Assign a label based on the error type to issues managed by the engine

Changed

• Breaking: Revise the formatting of reported issues, with notable adjustments to the title, transitioning from Fix <service_id> - <terms_type> to <service_id> ‧ <terms_type> ‧ not tracked anymore

Removed

• Breaking: No longer assign the label bot-report to issues managed by the engine

v0.31.1

0.31.1 - 2023-10-06

Full changeset and discussions: #1015.

Added

• Upgrade dependencies patches and ensure compatibility with Node v20

v0.31.0

0.31.0 - 2023-09-08

Full changeset and discussions: #1021.

Changed

• Breaking: Update opentermsarchive/terms-types dependency; update your declarations following the instructions in the changelog for validating declarations

v0.30.1

0.30.1 - 2023-09-06

Fixed

• Fix validation for removed terms types

v0.30.0

0.30.0 - 2023-07-10

Full changeset and discussions: #1015.

Added

• Embed Swagger UI for graphical user interface documentation of the API; access it on /docs

Changed

• Breaking: Change path from /services/:serviceId to /service/:serviceId for direct access to a service resource; update paths accordingly in your own codebase
• Breaking: Change path from /specs to /docs for OpenAPI specification; update paths accordingly in your own codebase and set the HTTP header Accept: application/json