v0.30.0-beta release

• Ability to create Weekly Notes? #416
• add note android app issue #415
• Create note info dialog #408
• Add import dialog #399
• Import & Export dialog show progress
• Arbitrary Code Execution #398
• Debian package support
• OPML 2.0 import/export, #286, #298
• In app help, #273
• Save electron window size and position #186
• Global menu with access to e.g. SQL console and Dev tools
• SQL console now shows schema for all tables

Database changes and script migration

This version brings a change in the DB structure - content of the note is now stored in a new table note_contents. This is done to improve scalability/performance - operations working on Note entities needlessly fetched note content (because it was part of Note entity) even though it was not used. This was particularly bad for large notes and when working with a lot of them (e.g. searching by label). Now content is loaded only when explicitly needed.

This requires changes in scripts which read/write note content. Example of previous usage:

note.content
// =>
await note.getContent(); // returns JSON object of the note content

note.jsonContent;
// =>
await note.getJsonContent(); // returns string

await note.getNoteContent(); // returns NoteContent entity

You can see detailed API for Note and NoteContent.

This change also necessitates update of the sync protocol so you will need to upgrade all instances simultaneously.