1.2.1 patch to fix annotation compatibility
Patch release to fix problem that would make any Wallabag annotation crash wallabako.
- update to wallabago v4 to fix change in wallabag annotations
Note that binaries are now compressed with gzip so that they can all be attached here. The OpenPGP signatures apply to the decompressed versions.
1.2.0 tag-filtering support
Minor release to ship patches accumulated in the last 9 months.
- add incomplete uninstall instructions
- add tag filtering support, thanks to Bogdan Cordier
- add a fully-populated config file to README
- add "say thanks", go report card and pipeline badges
- basic port to wallabago 2.0 library
- follow latest golang releases
- start using godep for dependency management
- fix linting in CI
- research the database format, abandon writing to the database which means no collection/shelf support will be possible on Kobo readers
1.1.1 yMerge changes from stable branch, including: * fix build with latest wallabago API changes
1.0.2 1.0.2 / 2017-06-20 ================== * fix build with latest wallabago API changes
1.0.1 1.0.1 / 2017-06-20 ================== Small bugfix release to help with 2.2 API without breaking backwards compatibility. * Make JSON requests to wallabag server
1.1.0 1.1.0 / 2017-03-07: Lost somewhere in time ========================================== This minor release was shipped to tag a bunch of changes that have been piling up since the last release, 4 months ago. Mostly documentation fixes, but also a small fix to better support the 2.2 API and allow for betting debugging output. * documentation improvements: * add TOC in troubleshooting section * document the database warning errors * document configuration file issues * move design notes to a separate document * add table of contents * add contribution guidelines * move known issues to the gitlab issue queue * add note about hardcoded settings * add -debug flag and configuration option * Dynamic path in CI script to work with forks * preliminary 2.2 API support: * Make proper JSON requests to wallabag server Thanks to Martin Trigaux for his contributions in this release!
This minor release was shipped to tag a bunch of changes that have been piling up since the last release, 4 months ago. Mostly documentation fixes, but also a small fix to better support the 2.2 API and allow for betting debugging output.
- documentation improvements:
- add TOC in troubleshooting section
- document the database warning errors
- document configuration file issues
- move design notes to a separate document
- add table of contents
- add contribution guidelines
- move known issues to the gitlab issue queue
- add note about hardcoded settings
- add -debug flag and configuration option
- Dynamic path in CI script to work with forks
- preliminary 2.2 API support:
- Make proper JSON requests to wallabag server
Thanks to Martin Trigaux for his contributions in this release!
1.0.0 Finally somewhere
This major release features complete configuration file support. Settings like
LogFilecan now be written directly into the
JSONconfiguration file. Logs, by default, are now disabled as they do not seem as useful anymore since things generally work well, hence the 1.0 release.
This release fixes a bunch of issues:
- extended configuration file support: logfiles, deletion, parallelism can now all be configured in the configuration file, see README for details
- do not delete articles by default: it causes spurious
triggers. this can be enabled again by adding the
Deletesetting with a
truevalue (note: no quotes) in the configuration file
- do not write a logfile by default: this takes up too much space and
doesn't seem very necessary anymore. this can be re-enabled by
LogFileparameter in the configuration file, set, for example, to
- drop support for the
-logfilecommandline flag, use shell redirection instead
- slow builds are now fixed now that the docker images have been updated
0.9 run forest
Lots of attempts to fix sync that was becoming increasingly unreliable.
- re-enable background processing which was disabled by mistake in 0.4
- increase delay to 15 seconds to try and fix sync issues
- try to remount internal drive if it's not remounted when we finish
- display human-readable elapsed time
- close database properly when completed
- write logs in /root/wallabako.log instead of storage
- output on console as well as logfile
- logfile rotation
Files and signatures:
0.8 Stop, don't do it.
- trigger wallabako only when the interface goes back up
- make version number less verbose for released versions
- make sizes human-readable
- handle download errors better
This release tries to fix weird issues with wallabako downloading files behind the library mountpoint.
0.7 Call of Chtulu
- add the
.txtextension to logfiles so that they are visible from the e-reader to improve debugging
- improve documentation significantly
- deal with corrupt JSON files better
- add -version flag to show version
- show version when we exit normally as well
This release is the direct result of hands-on usability testing with a non-technical user that gave great feedback. Thanks!
This time again, gitlab refuses the x86 upload, not sure why...
- add the
0.6 Look out honey, cause I'm using technology!
This feature release now will propagate read status to the Wallabag instance: your books marked as read on the e-reader will be marked as read on Wallabag as well! We also improve on the CI build time by using the new upstream stretch images which also means we're now running with the cutting-edge Go 1.8 version.
0.5 0.5: safety and liberty
This feature release starts looking into the Kobo database to see if a book is being read. If it is being read, it will not delete it. The next step is obviously to propagate the read status to the Wallabag instance, which is not done yet.
0.4 0.4: perfection is the ennemy of good
This is a small bugfix and documentation improvements release. This release should deal better with variable connection delays, as it can wait up to about 30 seconds.
0.3 release 0.3: practice makes perfect
Important bugfix release to deploy the correct binary but also changes location of files. Previously installed file will not be erased. This should have limited impact as the files were taking only 5MB on the system partition.
But if you want to clean up those files, you will need to hack your Kobo reader and run the following command:
rm -r /usr/local/wallabako
- use standard locations for programs (
/usr/local/bin) instead of our custom path (
- deploy the ARM binary properly (0.2 was deploying the x86_64 binary)
- logfile support, should be visible in
wallabako.login the top level directory of the reader
- information improvements: notify the user we are sleeping, etc
- delete old files by default: to get back to the old behaviour, you
need to edit
wallabag-runto remove the
- do not limit ourselves to 10 entries, but instead rely on the site
default (usually 30 articles), can be overriden with the
-countflag in the
- use standard locations for programs (
0.2 0.2 release: don't delete that file
This is a small bugfix release. It turns out that -delete was always enabled, even if the flag was not specified. Oops. Deleted files also didn't trigger a reload of the database, so now we count the number of deleted files, show the user, and properly execute the notify hook when files are deleted.
This release is the first published properly on Gitlab following their epic crash.
This release, exceptionally performed on Github because of a major outage at Gitlab is the first release of Wallabago. It ships with a tentative
KoboRoot.tgzthat is still untested.
More information in the README file.