[chore]: Prepare controller v6 Kiera #2735
Conversation
foxriver76
changed the title
|
Ev. add to BREAKING CHANGE and/or developer news (*) there seem to exits adapters still using siubscribe:messagebox. Repochecker can detect it. |
CHANGELOG.md
Outdated
| ## __WORK IN PROGRESS__ - Kiera | ||
|
|
||
| **Breaking changes** | ||
| * Support for Node.JS 16 is dropped! |
There was a problem hiding this comment.
| * Support for Node.JS 16 is dropped! | |
| * Support for Node.js 16 is dropped! |
CHANGELOG.md
Outdated
| **Features** | ||
| * (foxriver76) Added possibility to automatically upgrade adapters (see https://github.com/ioBroker/ioBroker.js-controller?tab=readme-ov-file#automatic-adapter-upgrade) | ||
| * (foxriver76) if updates for OS packages are available a notification is generated (Linux only) | ||
| * (foxriver76) js-controller (and thus the whole ioBroker) is now running as an ESM module internally while staying a 100 % backward compatible to adapters written in cjs |
There was a problem hiding this comment.
I would move this to the developer section
CHANGELOG.md
Outdated
| * (foxriver76/bluefox/Apollon77) minor fixes and stability improvements | ||
|
|
||
| **Developer relevant DEPRECATIONS/WARNINGS** | ||
| * (foxriver76) adapters need to use `adapter-core` version 3.1.4 or higher |
There was a problem hiding this comment.
with the peer deps maybe "telling 3.x (ideally 3.1.4+)" or such is sufficient?
CHANGELOG.md
Outdated
| * (foxriver76) js-controller (and thus the whole ioBroker) is now running as an ESM module internally while staying a 100 % backward compatible to adapters written in cjs | ||
| * (foxriver76) the controller creates a notification if free disk space is critical (see https://github.com/ioBroker/ioBroker.js-controller?tab=readme-ov-file#disk-space-warnings) | ||
| * (foxriver76) allow to ignore specific adapter versions (see https://github.com/ioBroker/ioBroker.js-controller?tab=readme-ov-file#ignoring-specific-adapter-version) | ||
| * (foxriver76) generate notification if an adapter is blocklisted and thus stopped |
There was a problem hiding this comment.
i would turn that around because foirst of all we stop adapters nochactively .. and generate notifies, right?
CHANGELOG.md
Outdated
| * (foxriver76) we provide all exports as ESM and as CJS to allow adapter developers to choose what to use | ||
| * (foxriver76) added convenient methods to manage node modules (see https://github.com/ioBroker/ioBroker.js-controller?tab=readme-ov-file#managing-node-modules) | ||
| * (foxriver76) allow to specify reason and exit code on `adapter.stop` | ||
| * (foxriver76) if you blocklist a version in the repository the controller won't start it anymore and will generate a notification |
There was a problem hiding this comment.
"... in your package.json and publish to github"? instead "repository"
There was a problem hiding this comment.
io-pack yeah makes sense
| * (foxriver76) added convenient methods to manage node modules (see https://github.com/ioBroker/ioBroker.js-controller?tab=readme-ov-file#managing-node-modules) | ||
| * (foxriver76) allow to specify reason and exit code on `adapter.stop` | ||
| * (foxriver76) if you blocklist a version in the repository the controller won't start it anymore and will generate a notification | ||
| * (foxriver76) for adapters of type `schedule` and `connectionType` set to `cloud` the schedule will be automatically delayed by up to 60 seconds randomly per user if the CRON does not contain a seconds argument, this is to prevent DDoS attacks |
There was a problem hiding this comment.
Should we then update the weather adapters that got manually added a delay logic adjust to set seconds?
There was a problem hiding this comment.
We could remove the workarounds their then but this requires controller v6 then of course, so maybe keep it for now?
No description provided.