Code blocks had more padding at the top than at the bottom, so their text sat off-center. This finishes the centering fix from #1461, part of which was lost in a merge.
Co-authored-by: noamp09 <noamp09@gmail.com>
The default warning badge is white on solid amber, roughly 1.7:1, which is hard to read in light mode and worse in dark. It now uses a tinted background with text in the same hue, dark gold on light and light amber on dark, matching how the rejected-row highlight is already drawn. The class is used only on the disposition timelines.
Invalid CVE records against Open WebUI keep circulating, and the pages meant to answer them said too little about why. Some records name the wrong product entirely, some rest on a mechanism the quoted code rules out, and some were published without the report ever reaching us, which would have made a live zero day had the finding been real. Minting a record takes days and removing one takes months, and several vulnerability databases never process the withdrawal at all, so an identifier the issuing CNA has formally rejected keeps displaying to their customers as a live finding.
The Vendor Dispositions index now states the project's position on the CVE system directly: we use it, we request identifiers for genuine findings, and these are the specific ways records filed against us have failed. It also says plainly that we will not ship a token fix to make an invalid record disappear, because rejection is the only route that improves the data everyone downstream depends on. The security policy's foreign-CNA rule links to that reasoning rather than asserting itself.
Supply Chain and Security Scanners becomes a folder, keeping its URL, and gains one page per vulnerability database: what that database still shows, how it compares to the CNA's own classification, and a dated log of every contact attempt. Twelve disposition timelines gain their follow-ups and the escalations back to the CVE Program Root, and the pages carry styled blocks marking the refutation, the withdrawal and the events that remain open.
The selected suggestion row and matched terms fall back to
--ifm-color-primary, which is #ddd in dark mode, leaving forced white text
on a light grey row. Set the search plugin's own colour variables for dark
mode instead: white marks on the dark dropdown and an inverted selected row
(white background, near-black text).
Swap docusaurus-lunr-search for @easyops-cn/docusaurus-search-local. All
query words are now required to match instead of being OR-ed, so a page
spamming one common word no longer outranks the page containing the whole
query. Underscore-joined names like CONTEXT_COMPACTION_TOKEN_CAP are
indexed both whole and as sub-words, matched terms are highlighted on the
target page, and a full results page is available at /search.
Add an exact-match layer on top (src/client/exactSearch.js, wired via
webpack module replacement). Multi-word or quoted queries that occur
verbatim on a page always rank first, rendered as a single marked phrase
with a section-anchor deep link, with token-based results following. A
SearchBar wrapper (src/theme/SearchBar) highlights exactly the searched
sentence on the target page and scrolls it into view, replacing the
per-word highlight parameters for these results.
Also mention the Builtin Tools capability name on the tools page so the
in-product term is findable by search.
Timothy Jaeryang Baek
Classic298andnoamp09
silentoplayz
Claude
Robin