-
Notifications
You must be signed in to change notification settings - Fork 72.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dev - candidate for release 15.0.0 #7809
Conversation
…already merged his branch to dev add NodeJS 16.x support. drop NodeJS 12.x support.It reached End-of-Life status on 30 April 2022 allow NodeJS 18.x support to run for CI upgrade webpack and webpack-cli update browserlist and browser documentation, config is now at .browserslistrc update README.md for browsers and Node versions fix typos in comments in lib/client/hashauth.js and webpack/webpack.config from #7440
…k.json with node v10.24.1
…verage pacakge (see issue #7515 ).
…odules, so the content is retained across cached builds in various PAAS environments
* Change | to && in package.json
… into PieterGit-dev20220815
The '^' prefix makes this meaingless, there's no reason to refuse to run less than 16.16.0 if it's still some 16.x.
…0815 Wip/bewest/pieter git dev20220815
New build artefact cache location
Avoid HTML injection called out by CODEQL.
See if this makes codeql happy.
Wip/bewest/code ql analysis
codeql text/html injection in food.js
…eads Wip/bewest/api secret free reads
Please see nightscout/nightscout-connect#18 for the proposed code change.
APIv3 sync only on srvModified
README.md: use shareous1 for Nightscout connect using Dexcom share
Point readme to correct location of swagger.yaml
👍 |
Given node 18 and 20, allow running on any LTS version of node. We can block out bad versions if needed.
Use npm install under node 14 generates different lock file.
This patch adjusts the user feedback while the server is initializing to communicate that Nightscout startup sequence should take closer to 15 second than 5 seconds.
Record output of npm instlal using oldest supported version.
Record changes from upgrading nightscout-connect to at least the latest release, 0.0.12.
Mongo driver update & less frequent database polls
@MilosKozak This completes all the high priority items. I've updated the draft release notes in the description. Please attach any additional feedback and I will release accordingly. Did we pick an |
@bewest no issues 👍 |
@bewest @MilosKozak In breaking changes it must be added that AAPS 3.1.0.3 and older versions of AAPS is not working with NS15. AAPS 3.1 users must stay on old master NS14. I assume there is no plan of making AAPS 3.1 compatible with NS15 due to imminent release of AAPS 3.2 that requires NS15 or that it was known that AAPS 3.1 didnt work with NS15? If it can be hotfixed to work with AAPS 3.1 it would save us all alot of trouble :) |
Draft Release notes
Nightscout version 15.0.0
Current dev branch preparing release for
15.0.0
. This is a major version bump because we changed node version requirements to support onlylts
versions, removing older versions.Breaking changes:
Fixes
Improvements
Loop
Android APS
While using websockets in NS v3 plugin treatments entered through NS UI (plus button) and other applications using v1 API are not sent to AAPS. This will be fixed in future release of NS. Always use the same client (v1 or v3) in AAPS and AAPSClient until NS fully switch to v3 internaly. The same is valid for AAPS and AAPSClient itself.
See the full release notes for AAPS 3.2.0 for more details.
Maintenance