Bot releases are visible (Hide)
Published by github-actions[bot] 5 months ago
Published by github-actions[bot] 5 months ago
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 6 months ago
Published by github-actions[bot] 7 months ago
Full Changelog: https://github.com/go-shiori/shiori/compare/v1.6.0...v1.6.1
Published by github-actions[bot] 7 months ago
It's finally here! After some work we have started moving towards a more usable and open API for others to consume, with proper session handling (no more random logouts on server shutdowns!), improvements to ePubs, UX and some more!
See details below for more information (important notes are the breaking changes) and please fill an issue if you see anything weird, better be safe than sorry!
serve
command is considered deprecated and will be removed in a future release. Right now just proxies to a new server
command that is the one that should be used from now on.--webroot
flag no longer modifies the routes internally, is up to the user to proxy the routes properly to Shiori without the prefix used to serve it.domain.com/shiori
you need to send the path back to Shiori without the /shiori
prefix so routes keep working. This can be done in most reverse proxies that we're aware of. We provided a sample configuration for Nginx. PRs are welcome for other reverse proxies.shiori/gopher
initial user is a full fledged user instead of being hardcoded into Shiori. If you want a new user you need to create a new owner user and then remove the shiori
user.Right now the release cadence has been slow because we made too many changes at once and we had to test and finish everything before doing this release. Plan moving forward is to iterate and release faster so we're planning smaller milestones to provide new features and fixes faster to you.
I will post an update announcement when the roadmap is reviewed.
Full Changelog: https://github.com/go-shiori/shiori/compare/v1.5.5...v1.6.0
Published by github-actions[bot] 9 months ago
Published by github-actions[bot] 10 months ago
Published by github-actions[bot] 10 months ago
Published by github-actions[bot] 12 months ago
Full Changelog: https://github.com/go-shiori/shiori/compare/v1.6.0-rc.3...v1.6.0-rc.4
Published by github-actions[bot] about 1 year ago
Full Changelog: https://github.com/go-shiori/shiori/compare/v1.6.0-rc.2...v1.6.0-rc.3
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Published by github-actions[bot] about 1 year ago
Full Changelog: https://github.com/go-shiori/shiori/compare/v1.5.4...v1.5.5
Published by github-actions[bot] over 1 year ago
Full Changelog: https://github.com/go-shiori/shiori/compare/v1.5.5-rc.1...v1.5.5-rc.2
Published by fmartingr over 1 year ago
Full Changelog: https://github.com/go-shiori/shiori/compare/v1.5.4...v1.5.5-rc.1
Published by github-actions[bot] over 1 year ago
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.
Full Changelog: https://github.com/go-shiori/shiori/compare/v1.5.3...v1.5.4
Published by github-actions[bot] over 2 years ago
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...
Published by github-actions[bot] over 2 years ago
Full Changelog: https://github.com/go-shiori/shiori/compare/v1.5.1...v1.5.2