gbv / jskos-server

Web service to access JSKOS data
https://coli-conc.gbv.de/api/
MIT License
6 stars 4 forks source link

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

Closed stefandesu closed 1 year ago

stefandesu commented 1 year ago

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?

stefandesu commented 1 year ago

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

stefandesu commented 1 year ago

To-Dos before release

To-Dos after release

stefandesu commented 1 year ago

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

Breaking Changes

Further Changes

stefandesu commented 1 year ago

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 commented 1 year ago

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.