Require Node.js 18 (and release a new major version)

[stefandesu]

The EOL of Node.js 16 is approaching (in September 2023), and Node.js 14 is almost EOL (end of April 2023), so it might be reasonable to skip both of those and require Node.js 18 for JSKOS Server. For this, we should release a new major version, i.e. version 2.0.0.

I'm not sure if there are other breaking changes that we could include in this release. @nichtich?

• /data endpoint should support concordances and mappings as well #193 could be considered a breaking change, and it's also easy to implement, so it should be part of v2.
• I would like to move to ES modules, see Update project to ESM #159.
  • Followed by finally updating all dependencies to their latest versions. (Tracking dependencies #140)
• Extend negative assessing annotations with predefined comments #194 is necessary for a new feature in Cocoda, so we should clarify and implement it (should also be fairly easy).
• We should check if JSKOS Server is affected by this issue: Database connection issues when using Node.js 17 or later on ARM64 devices login-server#98
• Issue with PATCH /concordances (and possibly annotations) #199

[stefandesu]

I think we'll be able to release it next week. 👍

[stefandesu]

To-Dos before release

• Do some manual integration testing with Cocoda, Login Server, and maybe BARTOC
• Prepare release notes
• Question: Can we adjust our automatic updates that they won't do major updates without confirmation?

To-Dos after release

• Import mismatch vocabulary into our main instances
• Adjust config to allow using mismatch vocabulary
• Make necessary adjustments in cocoda-sdk and release a new major version
• Check for required adjustments in other projects (BARTOC in particular)
  • Should be fine as long as updated cocoda-sdk is used
• Check whether everything works in our release instances

[stefandesu]

Suggestion for release notes (note that links don't work until the release is out):

Breaking Changes

• Node.js 18 is now required. (Require Node.js 18 (and release a new major version) #195)
• The Docker image was moved from coliconc/login-server to ghcr.io/gbv/login-server. See the Docker README for more information about Docker usage.
• The GET /data endpoint was completely adjusted. It now returns items of any kind by their URI. See documentation for more information. (/data endpoint should support concordances and mappings as well #193)
• Concept write access was moved to the new /concepts endpoint, i.e. POST/PUT/PATCH/DELETE /data is replaced with POST/PUT/PATCH/DELETE /concepts. (/data endpoint should support concordances and mappings as well #193)
• All old concept endpoints (/narrower, /ancestors, /search, /suggest) are now available under the /concepts endpoint, e.g. /concepts/narrower. The old concept endpoints are still available as deprecated aliases, but will be removed in the next major release. (/data endpoint should support concordances and mappings as well #193)
• All PATCH endpoints now merge data only on the top level. To remove top-level properties via PATCH, set them to null. (Issue with PATCH /concordances (and possibly annotations) #199)

Further Changes

• Add GET /concepts endpoint that implements previous behavior of GET /data for concepts only. (/data endpoint should support concordances and mappings as well #193)
• Negative assessment annotations can now include a mismatch tag for mappings. See documentation for further details. (Extend negative assessing annotations with predefined comments #194)
  • Support for this will be added to Cocoda in an upcoming release.
• The properties parameter was updated. See documentation for further details.
• Fix issues with MongoDB connection in Node.js 18.
• Code base was refactored to ESM. (Update project to ESM #159)
• Update all dependencies to their latest version. (Tracking dependencies #140)

[stefandesu]

v2.0.0 is now released: https://github.com/gbv/jskos-server/releases/tag/v2.0.0

I noticed a small issue that I fixed in v2.0.1: https://github.com/gbv/jskos-server/releases/tag/v2.0.1

This release also caused Cocoda to stop working until I updated it because it increased the API version to 2.0 as well, and Cocoda was configured to only support JSKOS API 1.0. This also means that none if the Cocoda versions in our archive work anymore which is a bit sad. Any ideas @nichtich? Related: #201 (One workaround could be to rebuild all Cocoda versions in our archive to skip the JSKOS API version check...)

[stefandesu]

One workaround could be to rebuild all Cocoda versions in our archive to skip the JSKOS API version check...

This is probably a one-liner fix + rebuild of all old version for the archive, but currently not a priority.

Make necessary adjustments in cocoda-sdk and release a new major version

I had this on the to-do list here, but since it's not related to jskos-server itself, I created a separate issue over in cocoda-sdk.

With this, I'm finally closing this issue.