This release of Firefly III introduces a new command that will decrypt your database. If this command is not executed at the proper moment, you could break your database. Make sure you have a backup before you begin and read the upgrade instructions. Generally speaking, Docker and Composer based installations should be fine. But when in doubt, tread carefully.
Added
- Experimental audit logging channel to track important events (separate from debug logging).
Changed
- Issue 2003, issue 2006 Transactions can be stored with a timestamp. The user-interface does not support this yet. But the API does.
- Docker image tags a new manifest for arm and amd64.
Removed
- skuzzle removed an annoying console.log statement.
Fixed
- Issue 2048 Fix "Are you sure?" popup, thanks to @nescafe2002!
- Issue 2049 Empty preferences would crash Firefly III.
- Issue 2052 Rules could not auto-covert to liabilities.
- Webbased upgrade routine will also decrypt the database.
- Last use date for categories was off.
API
- The
date-field in any transaction object now returns a ISO 8601 timestamp instead of a date.
Never heard of Firefly III? Check out the documentation and be sure to read the introduction and the grand theory to get an idea of what Firefly III is.
Check out the full changelog.