The component changed from rendering as a <a> to a <button>. This works for the menu, and is required by Reach - but is not acceptable for our UX. The primary function of this component is to let users click to navigate to "Code search". Rendering a button breaks a lot of functionality around that (e.g. middle mouse clicks to open in a new tab).
As far as I can tell, the Reach Menu components do not support rendering a MenuButton as a Link. I will look further if we can somehow achieve this. I will also speak to design to understand if we can move away from this UX - as I'm not sure that it will ever be fully accessible whilst we need to support both link and menu functionality simultaneously.
