Closed mpvader closed 1 year ago
I am now retrieving this, which has been automated, so it can be periodically ran. Question is where the output should go then.
package | releases | our version | available version | up to date | comment |
---|---|---|---|---|---|
nodejs | releases | 18.16.0 | 18.17.1 | :red_circle: | LTS |
signal-k server | releases | 1.46.3 | 2.1.1 | :red_circle: | |
signalk-venus-plugin | releases | 1.30.2 | 1.32.0 | :red_circle: | |
node-red | releases | 3.0.2 | 3.0.2 | :white_check_mark: | |
signalk-n2k-ais-to-nmea0182 | releases | 1.3.1 | 1.3.1 | :white_check_mark: |
I think it doesn't need to go anywhere. I mainly wanted you to check it, and take action on it: prepare a branch, or branches, that take care of this all.
I tested signalk-server 2.1.0, and it seems to work well, and its not as a major update as it seems like by going at the version number, ergo: pls prepare the signalk-server update as well.
venus-signalk plugin has been updated. Rest has deliberately not been updated.
closing, and there will be a new one for v3.20
Hi Dirk-Jan,
this is the first version of an aim to check that a bit more structurally on a regular basis. Can you check them when you're back?