Skip to content

Releases: stumpapp/stump

v0.0.7

12 Oct 18:01
@github-actions github-actions
v0.0.7
d216303
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.0.7 Latest
Latest

⚠️ This version contains breaking changes which will likely cause all books, series, and related entities (e.g. reading progress) to be dropped from the database. Please back up your existing database file before updating. You can restore the lost data using the attached resolve-missing-data.sql SQL script. The contents are as follows:

-- This SQL file is used to 'fix' the data in the database after the migration. BE SURE TO BACKUP BEFORE UPDATING:

-- 1. open the newly migrated database in your preferred SQLite client, I use TablePlus but it doesn't matter. You may also use the CLI e.g. sqlite3 stump.db < resolve-missing-data.sql
--    you must use absolute paths to the databases, replace with your path
ATTACH DATABASE '/replace/with/full/path/to/stump-before-migration.db' as 'backup';

-- 2. run the following SQL to copy the data from the old database to the new database, the tables we want data from are:
--    - `series`
--    - `series_metadata`
--    - `media`
--    - `media_metadata`
--    - `media_annotations`
--    - `reading_sesssions`
--    - `finished_reading_sessions`
-- The order is somewhat important, even though we adjust the PRAGMA foreign_keys = OFF; it is a safe precaution to follow the order above
BEGIN;
PRAGMA foreign_keys = OFF;
INSERT INTO series SELECT * FROM backup.series;
INSERT INTO series_metadata SELECT * FROM backup.series_metadata;
INSERT INTO media SELECT * FROM backup.media;
INSERT INTO media_metadata SELECT * FROM backup.media_metadata;
INSERT INTO media_annotations SELECT * FROM backup.media_annotations;
INSERT INTO reading_sessions SELECT * FROM backup.reading_sessions;
INSERT INTO finished_reading_sessions SELECT * FROM backup.finished_reading_sessions;
PRAGMA foreign_keys = ON;
PRAGMA foreign_key_check;
COMMIT;

You may execute the script using the CLI:

sqlite3 stump.db < resolve-missing-data.sql

This should restore all of the dropped data, however I can't make guarantees it would work for everyone and their setup. You may also just issue a scan and it will populate all but the reading progress.

What's Changed

New Contributors

Full Changelog: v0.0.6...v0.0.7

Contributors

JMicheli, aaronleopold, and 2 other contributors
Assets 7
Loading

v0.0.6

07 Sep 00:27
@github-actions github-actions
v0.0.6
7f73431
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.0.6

ℹ️ This release contains a tentative fix for a very large performance regression relating to ZIP file processing. See #435 for additional details.

What's Changed

New Contributors

Full Changelog: v0.0.5...v0.0.6

Contributors

wolffshots, JMicheli, and 2 other contributors
Assets 6
Loading

v0.0.5

16 Aug 00:36
@github-actions github-actions
v0.0.5
f8f0d3d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.0.5

⚠️ IMPORTANT: This is the first release with binary assets included. I have only had time to test the macOS (ARM) binary, and I have discovered a bug where the default config (~/.stump/Stump.toml) is not initialized correctly. This probably affects all of them, and will be fixed by the next release. You will need to update the profile to be release and update the client_dir accordingly (by default, it should be ./client). You may also prepend the environment variables on the first run to write the config for you:

STUMP_PROFILE=release STUMP_CLIENT_DIR=./client ./stump_server

A HUGE thank you to @JMicheli to getting the binary release workflow to the finish line. If you encounter any issues, please reach out! 🙂

What's Changed

New Contributors

Full Changelog: v0.0.4...v0.0.5

Contributors

fehwalker, JMicheli, and aaronleopold
Assets 6
Loading

v0.0.4

11 Jul 01:33
@aaronleopold aaronleopold
v0.0.4
c0c4267
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.0.4

What's Changed

Full Changelog: v0.0.3...v0.0.4

Contributors

JMicheli and aaronleopold
Assets 2
Loading

v0.0.3

18 May 16:44
@aaronleopold aaronleopold
v0.0.3
ef8b97a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.0.3

What's Changed

New Contributors

Full Changelog: v0.0.2...v0.0.3

Contributors

JMicheli, PragmaTwice, and aaronleopold
Assets 2
Loading

v0.0.2

22 Apr 03:51
@aaronleopold aaronleopold
v0.0.2
bd8442d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.0.2

What's Changed

New Contributors

Full Changelog: v0.0.1...v0.0.2

Contributors

yoav-lavi, JMicheli, and 2 other contributors
Assets 2
Loading

v0.0.1

18 Feb 15:31
@aaronleopold aaronleopold
v0.0.1
3ecf4fb
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.0.1 Pre-release
Pre-release

What's Changed

Read more

Contributors

tuxuser, f8thl3ss, and 7 other contributors
Assets 2
Loading