fix(container): update image ghcr.io/new-usemame/calibre-web-nextgen ( v4.1.20 ➔ v4.1.21 )#2475
Merged
mrdynamo merged 1 commit intoJul 26, 2026
Conversation
…( v4.1.20 ➔ v4.1.21 )
Contributor
Author
konflate — summaryNote +0 added · 2 changed · −0 removed — 2 resources · 2 apps Tip Routine — only container-image and chart-version changes; nothing else changed. Blast radius
Image changes
konflate · rendered |
There was a problem hiding this comment.
ghcr.io/new-usemame/calibre-web-nextgen: v4.1.20 → v4.1.21
Verdict: Safe to merge
Breaking changes: None.
Deprecations: None. The default robots.txt policy now asks crawlers to stay out; if you actually want the library indexed, drop a custom robots.txt next to app.db in the config folder and it takes precedence. This is opt-out, not a forced change.
Notable behavior changes worth knowing about:
- Guest reading is restored when anonymous browsing is enabled — the new interface was signing guests out, the classic reader was crashing, and the reader was waiting forever for personal settings guests don't have. All three paths are fixed. This repo's HelmRelease doesn't set anonymous browsing, so the setting is whatever the running Calibre configuration has — worth a quick check after merging if guests are meant to use the library.
robots.txtnow returns a real disallow policy instead of a 404. The repo's external HTTPS route exposes this app publicly, so the new behavior is the safer default — search engines will stop indexing what was previously a404they were free to crawl./kosync/exportnow includes book identifiers (ISBN, Goodreads, Amazon, custom) and un-escapes author names properly. This is a strict superset of the prior payload — any external progress tracker consuming this endpoint should ignore unknown fields, but if a homegrown consumer is strict about keys, it may need a small update.- KOReader email-send sync is now registered the same way as downloads, so
Send to Readerover email will sync reading position. Previously, the server silently dropped the fingerprint and the log saidNo book found for checksum. This is a fix, not a change. - Unreferenced static icons (
cps/static/icon.png,icon.svg) were removed. Nothing in this repo references them, so no fallout. - iOS home-screen icon fix only affects clients adding the library to their home screen — no cluster-side change.
Sources consulted:
- https://github.com/new-usemame/Calibre-Web-NextGen/blob/HEAD/CHANGELOG.md
- new-usemame/Calibre-Web-NextGen@v4.1.20...v4.1.21
- #2475
- #2465 (prior v4.1.19 → v4.1.20 review context)
robot-rosey
Bot
deleted the
renovate/ghcr.io-new-usemame-calibre-web-nextgen-4.x
branch
July 26, 2026 18:02
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
v4.1.20→v4.1.21Release Notes
new-usemame/Calibre-Web-NextGen (ghcr.io/new-usemame/calibre-web-nextgen)
v4.1.21Compare Source
Added
GET /kosync/exportpreviously handed out only title and author, which is ambiguous for reissues, translations and common titles, and left the receiving service to guess. Every exported book now carries anidentifiersmap holding whatever Calibre has for it (ISBN, Goodreads, Amazon, and any custom types), or an empty map when the book has none. Contributed by @Kyraminol (#1092).Fixed
Uploading a new cover now shows the new cover. Replacing a book's cover from the edit page appeared to do nothing — the image on the left kept showing the old one, so it looked like the upload had failed even though it had worked. The cover lives at a fixed address, so the browser kept serving the copy it already had. The preview now updates the moment the upload finishes. Reported by @chloeroform (#989).
On a phone, the Edit button no longer sits on top of "Read now" on a book cover. The label was clipped to "Read no…" because the pencil overlapped its tail — 52 pixels of it, on both phone and tablet widths. Both controls are permanently visible on a touch screen, so this was what every phone user saw rather than a hover quirk. The label now keeps clear of the button at every width, and cards you can't edit still centre it as before. Reported by @Andrew-H2O (#1112).
Search engines are now told not to index your library.
robots.txtpointed at a file that had never existed, so every install answered "not found" — inherited from upstream Calibre-Web, where it is also missing. A crawler that gets no answer falls back to its own rules and indexes whatever it can reach, which on a server with guest browsing enabled is your catalogue, and by extension what the people using it read. The server now returns a policy that asks crawlers to stay out. If you deliberately want your library indexed, put your ownrobots.txtnext toapp.dbin the config folder and it will be used instead — no rebuild, and it survives upgrades (#1104).Books you email with "Send to Reader" now sync your reading position. If you send books to your e-reader by email rather than downloading them, KOReader would push your progress and the server would quietly drop it — the position was saved but never attached to the book, so the library showed nothing and the log said
No book found for checksum. The same book fetched over OPDS synced fine, which made it look like a device problem. The cause was on our side: the server recognises a book by fingerprinting the exact file it hands out, and it fingerprinted downloads but never the copy it emailed — which, with metadata embedding on, is a different file. Emailed books are now registered the same way downloads are, under both content and filename matching. Reported by @uschi1 (#627).The quick tag box on a book page now suggests tags you already use. Adding a tag from the book page offered no suggestions, so it was easy to type "sci-fi" once and "Sci-Fi" the next time and end up with two tags meaning the same thing — which is exactly what two people asked for after the full editor got suggestions and this field didn't. It now offers matching tags as you type, skips the ones the book already has, and still lets you type something new. Arrow keys move through the list, Enter picks, Escape closes. Reported by @magdalar (#741, #572).
When KOReader says "Server push failed", the server now records why. Highlight sync gives the reader one message and no detail, and the server was writing nothing at all about it — a rejected push, a book it couldn't match, and a highlight it declined to store all left the log completely empty, so there was no way to tell them apart from the outside. Two of those cases even answered "success", which meant the reader reported the sync as fine while nothing had been saved. Every highlight sync now leaves a line naming the book and what happened to it — how many highlights were stored, deleted or dropped, and for a refusal, which field was wrong. Anyone chasing a highlight-sync problem can now get the answer from
docker logs. Reported by @iroQuai (#920).Guests can open and read books again. On a server with anonymous browsing enabled, a visitor who clicked "Read" got an error page in the classic view and was bounced back to the home page in the new interface — no book, no explanation. Three separate faults stacked up on that one click: the classic reader crashed before it could render, the new interface mistook "this visitor is a guest" for "this visitor's session expired" and signed them out, and the reader then waited forever for personal settings a guest never has. All three are fixed, and a guest now reads with the default appearance while signed-in readers keep their saved theme, font and position. Reported by @bentsea (#1074).
Author names in the reading-progress export no longer come out with a stray
|where a comma belongs. An author stored in Calibre as "William H. Keith, Jr." was exported as "William H. Keith| Jr.", because Calibre escapes a comma inside a single author name andGET /kosync/exporthanded the stored form out unchanged. Any service ingesting the export was matching against a name no catalogue lists. The rest of the app already un-escaped it; the export now does too.Firefox no longer draws permanent scrollbars down the side of the page. Firefox 153 changed how it treats one of the scrollbar rules the app was using, and the effect landed the day people updated: bars that used to fade away when you stopped scrolling became fixed, always-on, and squeezed the content beside them. In the new interface that hit the sidebar and the Discover row; the classic theme had the same thing on both columns of every page. Both are fixed — the app now describes scrollbars using the standard properties, so Firefox goes back to its own fading scrollbars, and the slim dark styling is unchanged in other browsers. Reported by @chloeroform (#1089).
Adding the library to an iPhone or iPad home screen now gives you the app icon instead of a screenshot of the page. Every page offered iOS an
.icofile as its home-screen icon, and described it as a size that file does not contain. iOS cannot use an.icothere, so it gave up and used a thumbnail of whatever page you happened to be on. The correctly sized icon had been sitting in the app unused the whole time; every page now points at it, and the same fix applies to the new interface and to servers running behind a reverse proxy on a sub-path.Removed
cps/static/icon.pngandicon.svgwere the icons used beforefavicon.icoreplaced them, and nothing had pointed at them since. They were still being shipped in every release, so every download carried about 29 KB of files no browser ever asked for. Reported by @chloeroform (#1095).Changed
Configuration
📅 Schedule: (in timezone America/Chicago)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate.