This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch dependabot/pip/pelican-4.12.0
in repository https://gitbox.apache.org/repos/asf/solr-site.git
omit 4b23c4e42 Bump pelican from 4.11.0.post0 to 4.12.0
add 2593c48b7 Add Solr/Lucene migration correctness blog post
add aae498b1b Merge pull request #178 from
parveensaini/add-solr-lucene-migration-correctness-post
add f45895e61 Canned response A 30d->90d
add 6ce19c8dd Bump python from `01f1254` to `dd4d2bd` (#176)
add cfeeab4b7 Bump pip from 26.0.1 to 26.1 (#179)
add 51c7b2312 Fix bloghome template broken by Pelican 4.12.0 (#180)
add f69e2938a Bump pelican from 4.11.0.post0 to 4.12.0
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (4b23c4e42)
\
N -- N -- N refs/heads/dependabot/pip/pelican-4.12.0 (f69e2938a)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
Dockerfile | 2 +-
.../2026-05-02-solr-lucene-migration-correctness.md | 12 ++++++++++++
content/pages/security-reporting.md | 2 +-
requirements.txt | 6 +++---
themes/solr/templates/bloghome.html | 2 +-
5 files changed, 18 insertions(+), 6 deletions(-)
create mode 100644
content/pages/blogposts/2026-05-02-solr-lucene-migration-correctness.md
