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:
3.15
->3.16
Release Notes
lemon24/reader (reader)
v3.16
Compare Source
Released 2024-12-08
Parse and store :attr:
Entry.source
for Atom and RSS feeds. (:issue:267
)Entry.feed_resolved_title
and :attr:Feed.resolved_title
properties.feed
search column now indexes :attr:Entry.feed_resolved_title
,instead of feed :attr:
~Feed.user_title
or :attr:~Feed.title
.Add :func:
reader.utils.archive_entries
forcopying entries to an "archived" feed.
(:issue:
290
)~Reader.copy_entry
.Fix bug causing :class:
Reader
operationsfrom a thread other than the one that created the instance
to happen with foreign key constraint enforcement disabled
(e.g. deleting a feed from another thread would not delete its entries).
This bug exists since using :class:
Reader
instances from other threadsbecame allowed in
2.15 <Version 2.15_>
_.Serving the web application with
python -m reader serve
is known to be affected.
Serving it with uWSGI without threads (the default)
should not be affected.
.. attention::
Your database may be in an inconsistent state because of this bug.
It is recommended you run
PRAGMA foreign_key_check
_ on your database.If you are upgrading from a version prior to 3.16
(i.e. were not using a pre-release version of reader),
the migration will do so for you.
If there are inconsistencies, you will get this error::
Fix :meth:
~Reader.enable_search
/ :meth:~Reader.update_search
not working when the search database is missing but change tracking is enabled
(e.g. when restoring the main database from backup).
(:issue:
362
).. _PRAGMA foreign_key_check: https://www.sqlite.org/pragma.html#pragma_foreign_key_check
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.
Summary by Sourcery
Build: