Is this still happening? (Trying to rule out caching.) Also, congratulations!

@MonicaCellio Thanks :) It's still happening. I also hard refreshed, so I don't think it's a cache issue with my browser.

Thanks for checking. The other possibility was that we were caching it, though I'd expect us to refresh that at the same time we check/update abilities. So looks like a bug. Thanks for the report.

The check that decides what text to render in that location was checking for an ability with internal name 'edit_post', while the actual ability is called 'edit_posts' (note the 's').

Fix submitted, should be merged in the near future and all will be well with the deploy after merge

Monica Cellio‭ I thought the fix is already in. Current version is poining to the 9fdbbe185c40c61eb6175111423e75348e67f45e commit while fix is in 56a080f6a2a5ee599de493ce300cf5afa35d781b commit which is before. Or is it some kind of mess with commits history?

Sorry FoggyFinder‭ - I thought we were still waiting for deploy, but that's because I apparently shouldn't try to read commit logs before caffeine. :-) Moshi says it's fixed, so I've updated the tag.