Update dependency furo to v2023.8.19 #32
Keine Reviewer
Labels
Keine Label
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Kein Meilenstein
Kein Projekt
Niemand zuständig
2 Beteiligte
Nachrichten
Fällig am
Kein Fälligkeitsdatum gesetzt.
Abhängigkeiten
Keine Abhängigkeiten gesetzt.
Referenz: nick-slowinski.de/docs#32
Laden …
In neuem Issue referenzieren
Keine Beschreibung angegeben.
Branch „renovate/furo-2023.x“ löschen
Das Löschen eines Branches ist permanent. Obwohl der Branch für eine kurze Zeit weiter existieren könnte, kann diese Aktion in den meisten Fällen NICHT rückgängig gemacht werden. Fortfahren?
This PR contains the following updates:
==2023.7.26
->==2023.8.19
Release Notes
pradyunsg/furo (furo)
v2023.8.19
Compare Source
v2023.8.17
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 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 this update again.
This PR has been generated by Renovate Bot.
4fa721c74e
zufc821d83cc
force-gepusht VergleichenUpdate dependency furo to v2023.8.17zu Update dependency furo to v2023.8.19Sphinx 7.2.2 doesn't work with the notfound extension (see github.com/readthedocs/sphinx-notfound-page/issues/219).
I could pin Sphinx to <7.2 or just wait for fixes. 😅
Meanwhile
sphinx-notfound-page
has been updated to version1.0.0rc1
which should fix the issues, but i choose to not update to this rc version (there is no need to fix this issue quickly).fc821d83cc
zub2558eb322
force-gepusht VergleichenWaiting 1 hour for renovate to update this PR.
sphinx-notfound-page
has been updated to version 1.0.0 in #33 and the issue should be fixed now.b2558eb322
zufa34a7c418
force-gepusht VergleichenHi, @NickSlowinski can you review this pr?