Maybe unpopular opinion: NVDA should do more to maintain backwards compatibility of add ons. I've got a whole list of add ons that are now incompatible. Guess I'm not updating? Luckily I'm a developer and can do something about it when I have the time (whenever that actually happens), but not everyone is. Not getting into potential solutions here but there has to be a more user centric way to do what they need to do while minimizing user frustration.
in reply to Keri Svendsen

@sapphireangel @Lino_JR @cachondo @dhamlinmusic firstly, please do tag us (or at least use #nvda) if you want a response :) So 1) if we never updated, we'd still be on Python 2, which reached end of life 6 years ago. 2) Add-ons can potentially use ANY function or call within Python - we can't possibly support or even check them all. 3) We ARE doing something about this - we are working on a secure add-on API which will resolve breaking changes 1/2
in reply to NV Access

@sapphireangel @Lino_JR @cachondo @dhamlinmusic 2/2 4) We only break backwards compatibility once a year, not every release, and 5) We really couldn't have made it any easier to override the compatibility check if you so desire. It's right there in the add-on store, no need to go in and edit files manually. We warn that ONLY stops NVDA checking the version number, it doesn't comfirm it actually works. With 2025.1 only released yesterday, over 75 add-ons in the store are updated
in reply to Mike Forzano

@sapphireangel @cachondo @dhamlinmusic As things are now, there really isn't any way of knowing which add-ons will be affected - so we really can't make a blanket statement about what will and won't be affected, which is why we ask add-on developers to check their add-ons and declare compatibility. Yes it's Python upgrades but also other dependency and internal changes (EG "Speak Typed Characters" now has three options, it's not just a boolean on / off anymore).
in reply to Mike Forzano

@sapphireangel @cachondo @dhamlinmusic No, but it will provide a reliable way of doing at least common tasks. We know one of the benefits of NVDA is add-ons have access to the full power of Python. We don't want to take that away from add-on developers. I must admit I don't have all the details myself though so I'll try not to get into too much detail on things I'm not fully across - but we will certainly be in regular communication with the add-on community as this moves forward.