| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Jdlrobson | T195473 [GOAL] Invest in the MobileFrontend & MinervaNeue frontend architecture | |||
| Resolved | Jdlrobson | T195478 [EPIC] Speed up unit test execution and increase code coverage | |||
| Resolved | Jdlrobson | T195482 [EPIC] Review and refactor MobileFrontend components used by Minerva | |||
| Open | None | T281930 [EPIC] Migrate MobileFrontend's code to Vue.js and Codex | |||
| Open | None | T212465 [EPIC] None of our View's should exhibit 2 levels of inheritance | |||
| Stalled | BUG REPORT | None | T289084 MinervaNeue shows 2 search elements when JS is disabled | ||
| Open | None | T282473 [GOAL] Use the Codex search widget inside the mobile site | |||
| Resolved | Lucas_Werkmeister_WMDE | T281318 [EPIC] Enable new Codex Typeahead search on Wikidata.org | |||
| Resolved | Jdlrobson | T275251 New Vector Search is not Wikidata aware | |||
| Resolved | Lucas_Werkmeister_WMDE | T316093 Make new Vector search use wbsearchentities on Wikidata | |||
| Resolved | Michael | T326633 Monitor the deployment of the new Search on the 2022 version of the Vector skin |
Event Timeline
Mentioned in SAL (#wikimedia-operations) [2023-01-11T14:39:22Z] <lucaswerkmeister-wmde@deploy1002> Synchronized php-1.40.0-wmf.18/extensions/Wikibase/repo/resources/wikibase.vector.searchClient.js: Backport: [[gerrit:877972|Add missing parentheses to vector search match text (T326633)]] (1/2) (duration: 07m 09s)
Mentioned in SAL (#wikimedia-operations) [2023-01-11T14:46:37Z] <lucaswerkmeister-wmde@deploy1002> Synchronized php-1.40.0-wmf.18/extensions/Wikibase/repo/tests/jest/wikibase.vector.searchClient.spec.js: Backport: [[gerrit:877972|Add missing parentheses to vector search match text (T326633)]] (2/2) (duration: 06m 46s)
As far as I can tell, the deployment went without incident and I have heard nothing from the community about this.
That being said, we noticed that the new search has a different way of highlighting the searched term, which can result in strange looking results: T327510
However, that is an issue in itself and independent from the deployment, and thus does not block this task here.