v0.29.0: upgrade all crystal libraries

What's Changed

• upgrade crystal to 1.14.0 in #7,
• fixes logging issues #8 raised in getmango#338

Full Changelog: v0.28.2...v0.29.0

v0.28.2: improvements in chapters sort in a title

Note: As always, create a backup of your database specified in db_path before upgrading.

If you notice any issues in viewing library, just delete the db_path file and re-run the app. It will re-create the database, but with a fresh admin user credentials

What's Changed

• combine names that look similar in chapter sort by @vrsandeep in #6

Full Changelog: v0.28.1...v0.28.2

v0.28.1: more fixes for making the project run locally

What's Changed

• fix deprecation notice in Github action for releases: #4
• Make source maps for external javascript files locally available: #5

Full Changelog: v0.28.0...v0.28.1

v0.28.0: run the entire project without using external sources

What's Changed

• Merge changes from Rc/0.27.1 by from getmango#337
• setup CI to push container images to vrsandeep/manga in #2
• make external dependencies locally available in #3

Full Changelog: v0.27.0...v0.28.0

Breaking change for default config users

For older users of mango, who kept updating their containers to new releases, should also have taken care of this, but for those who directly started on last release of mango, read on.
Take a backup of your current database. It is located under db_path as defined in config.yml. It's value before this release is ~/mango.db. It needs to be placed at ~/mango/mango.db. See the change at getmango@61d6c2e

or follow getmango#341 (comment)

If this is not done, mango may crash the first time it launches the new image. Starting the container again will re-create the container from scratch.