Hi Christoph,
Thanks for your answer. It’s weird that I had this problem whereas I was already on 1.5.2 before updating (it was my first update, I got 1.5.2 when I activated n8n for the first time), but the name was still the old one (from before 1.5.1) 
About my “comment” (it wasn’t really a complaint 
), as I said, I know you do your best, and as I said, you do it pretty well in my humble opinion!
However, it is sometimes complicated to keep everything working after updates (you’ve seen I also encountered problems with the python API after this update), that’s why I opened this thread to see how it could be possible to think together of a solution to avoid side effects. As you answered me, this is a particular and pretty rare situation as it is a major version update.
Anyway, for this particular problem, it was disturbing, but no big deal to fix.
Bests,
Benjamin
