Skip to content

Releases: go-shiori/shiori

v1.6.0-rc.5

28 Dec 17:51
cf7301c
Compare
Choose a tag to compare
v1.6.0-rc.5 Pre-release
Pre-release

Changelog

v1.6.0-rc.4

08 Nov 22:24
7765e5b
Compare
Choose a tag to compare
v1.6.0-rc.4 Pre-release
Pre-release

Changelog

  • c64e858 Fix typos (#756)
  • f16dd42 Make suggestion clickable in bookmark creation (#765)
  • 013270a Update documentation for add links to shiori in android devices from share menu (#757)
  • f82b97d add create ebook by default in settings (#761)
  • 29b1d97 chore(deps): bump the all group with 1 update (#767)
  • 1d58455 chore: comment unused functions
  • 7765e5b chore: frontend formatting (#764)
  • c05d617 feat: allow per-user settings and store them in database (#639)
  • 1ae82f4 fix: Actions in overlays on mobile hard to press (#759)
  • 03df5e8 fix: allow webp thumbnails (#758)
  • 5e9847a refactor: migrate ebook routes to new http server (#742)
  • 106bf16 refactor: remove unneeded variable and unify the way send token in header (#763)

What's Changed

New Contributors

Full Changelog: v1.6.0-rc.3...v1.6.0-rc.4

v1.6.0-rc.3

09 Oct 16:24
46c1a6a
Compare
Choose a tag to compare
v1.6.0-rc.3 Pre-release
Pre-release

Changelog

  • 2c31048 chore(deps): bump golang dependencies (#746)
  • 36b0121 chore(deps): bump the all group with 6 updates (#738)
  • a3fb075 chore(deps):Update Github Actions dependencies (#740)
  • 46c1a6a feat: allow resize the dialogbox for bigger/hidpi screens (#732)
  • eb666cd feat: use new JWT auth in all frontend API calls (#743)
  • c6aabc4 fix: styles-check and swag-check monitor just needed directory not project root (#747)

What's Changed

  • feat: use new JWT auth in all frontend API calls by @fmartingr in #743
  • fix: styles-check and swag-check monitor just needed directory not project root by @Monirzadeh in #747
  • feat: allow resize the dialogbox for bigger/hidpi screens by @Monirzadeh in #732

Full Changelog: v1.6.0-rc.2...v1.6.0-rc.3

v1.6.0-rc.2

18 Sep 07:26
9e91029
Compare
Choose a tag to compare
v1.6.0-rc.2 Pre-release
Pre-release

Changelog

  • 9082f98 deps: upgrade to Go 1.21 (#698)
  • 4df7e1d feat: build css from less files locally (#735)
  • e722cb6 fix: properly parse mysql connection string, docs update (#730)
  • 3fb3f60 just use one dependency for uuid (#736)
  • 9e91029 refactor: Migrate ePub generation to go-epub (#679)

v1.6.0-rc.1

11 Sep 17:28
1d52569
Compare
Choose a tag to compare
v1.6.0-rc.1 Pre-release
Pre-release

Changelog

v1.5.5

26 Jul 06:36
e7faeaf
Compare
Choose a tag to compare

What's Changed

Features

Fixes

Other

New Contributors

Full Changelog: v1.5.4...v1.5.5

v1.5.5-rc.2

19 Jul 15:33
6f19c12
Compare
Choose a tag to compare
v1.5.5-rc.2 Pre-release
Pre-release

What's Changed

Full Changelog: v1.5.5-rc.1...v1.5.5-rc.2

v1.5.5-rc.1

09 Jul 06:59
e02d3e7
Compare
Choose a tag to compare
v1.5.5-rc.1 Pre-release
Pre-release

What's Changed

New Contributors

Full Changelog: v1.5.4...v1.5.5-rc.1

v1.5.4

21 Jan 08:09
9344bbe
Compare
Choose a tag to compare

Falling back to transparent migrations

After some discussion over #473, we've decided to roll back the change introduced in v1.5.3 that made the user take care of migrations manually.

What does this mean? Basically we added proper migrations into Shiori and added a custom command to perform them, but since our documentation is lacking in some ways most users where a bit confused about what a migration meant, specifically users of the CLI tool which do not rely on the server. In the end, and to avoid adding more complexity to the tool (which is one of the core features) I decided to rollback that change, meaning that everything should be done in the background while you use or serve Shiori. If anything goes wrong, you will get an error on the output which you can use to open an issue and your database should be left as it is.

What's Changed

  • fix invalid assets path when use webroot by @hulb in #448
  • feat: session expire time from backend by @fmartingr in #437
  • Fix docker migration script example by @kaimoe in #451
  • Improve performance for sqlite queries by @Orhideous in #425
  • fix: remove manual transaction on sqlite migration 2 by @fmartingr in #468
  • feat: upgrade to go 1.19 by @fmartingr in #469
  • docs: fix remember represented as a number instead of a bool by @babariviere in #472
  • refactor:pass ctx to db layer, return err instead of recover panic by @hulb in #450
  • fix(import): check for no rows error by @fmartingr in #487
  • fix err in keyword searching by @hulb in #494
  • fix(psql): save bookmarks not using passed bookmark id for the insert by @fmartingr in #484
  • fix: import should respect add_date or last_modified fields by @fmartingr in #490
  • fix: data dir permissions having execute for all by @fmartingr in #493
  • fix: remove CreateNewID usage from api handlers by @fmartingr in #486
  • fix: sharing context between api and goroutine caused goroutine to fail by @Acelya-9028 in #499
  • fix: saving bookmarks inconsistencies by @fmartingr in #500
  • chore(deps): updated go and github actions dependencies by @fmartingr in #511
  • fix: failed to save bookmark: constraint failed: UNIQUE constraint failed: bookmark.url by @Acelya-9028 in #515
  • fix: avoid panic usage when downloading bookmark by @fmartingr in #513
  • fix(db): avoid using dash in fts5 queries by @fmartingr in #514
  • fix(api-ext): use same save logic as the api by @fmartingr in #518
  • fix: remove createnewid usages by @fmartingr in #520
  • feat(frontend): username autofocus on login by @fmartingr in #519
  • Remove typo in compose Dockerfile post-run command by @AIndoria in #527
  • Make migrations transparent to the user by @fmartingr in #530
  • Fix #549 reset page when searching for new tag by @ryanwr in #550
  • deps: up to date by @fmartingr in #552
  • ci: fix goreleaser snapshots by @fmartingr in #553

New Contributors

Full Changelog: v1.5.3...v1.5.4

v1.5.3

23 Jun 07:21
f000f11
Compare
Choose a tag to compare

Breaking changes

  • Migrations: Migrations are now implemented in a manual and separate CLI command called migrate. Users need to perform database migrations previous to any other Shiori command in order for the database schema to be created:

    $ shiori add https://github.com
    Failed to create ID: SQL logic error: no such table: bookmark (1)
    exit status 1
    
    $ shiori migrate                  
    
    $ shiori add https://github.com   
    Downloading article...
    
    2. GitHub: Where the world builds software
       > https://github.com
       + GitHub is where over 83 million developers shape the future of software, together. Contribute to the open source community, manage your Git repositories, review code like a pro, track bugs and feat...
    

Changelog