chore(deps): update container image ghcr.io/go-shiori/shiori to v1.6.0@628826c by renovate #19427
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.5.5
->v1.6.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
go-shiori/shiori (ghcr.io/go-shiori/shiori)
v1.6.0
Compare Source
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!
Breaking changes
serve
command is considered deprecated and will be removed in a future release. Right now just proxies to a newserver
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.That means that if you want to serve Shiori under
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 theshiori
user.Release cadence
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.
What's Changed
New Contributors
Full Changelog: go-shiori/shiori@v1.5.5...v1.6.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.