v1.0.0

With 2020 coming to a close, @l3uddz and I worked on the last couple of tweaks to prepare Autoscan for 1.0.

Autoscan's 1.0 release guarantees that the config file and API will not see any major changes until a 2.0 release. In other words, no need to delete databases or change config files on 1.x version upgrades! In addition, the SQLite database will not be changed until a 2.0 release.

However, we can still add features to the config file and API as long as these are non-breaking.

OMG! A 1.0 release! Does this mean that Autoscan can be considered feature-complete?

Not yet! While the majority of features are in-place, there are still a couple of things (such as Jellyfin support) which are on our 1.x roadmap.

Okay... is it at-least bug-free then?

The core of Autoscan is considered bug-free. No bugs have survived the early access testing period.
However, two of Autoscan's dependencies, Bernard and FSNotify, are still hit-or-miss.

As the author of Bernard, I have not been able to track down the issues popping up for some users. Initially, Bernard was planned to become the building-block for many of my projects. However, the uncertain future of Google Drive has cancelled any future Bernard development.

Changelog

So, what changed?

New features

• Added a manual webhook/trigger for use by third party applications and scripts. d7d172b

Minor changes

• The time format in the logs now includes the date as well as the time in seconds. db7ee12