Peter Sobolewski

> Hm. What about linking to give nersion docs? So instead stable use tag? So that the menu link connects to the docs of the specific version? That would be...

> stable docs: https://napari.org/stable/index.html > > 0.4.16 docs: https://napari.org/0.4.16/index.html > > development docs: https://napari.org/dev/index.html Right, but is PRing the menu link every release the right idea? To keep the link...

> Do you mean about something like this to check the current napari version form the code? > > > > ```python > > In [1]: from packaging.version import parse...

> As napari does not provide stable API some plugin creators does not support all napari version and on this phase of development it is expected to people will use...

@Czaki using your code example with parse works for me locally on both 0.4.16 and `main` (dev). Seems like the best solution!

I swapped `napari info` to the bottom of the menu after a divider—this is typical on Windows, though the name is `About ...` not `... info`. Plus, I think it...

Great Idea! It would also ensure someone reaching docs from Help knows that they are running outdated napari. @brisvag BTW can you post a screenshot from non-macOS?

Of the contents of Help 🤣

Thanks @Czaki Guessing you're on dev branch? (No release notes shown). I think it looks good to me.

No, no, sorry I wasn't clear and was also obviously stupid—of course you're testing this PR branch not something else. Anyhow, I was just glad to see the check for...