Custom Tasks/Components - Changing Version W/o Breaking Packages

Whenever I make a breaking change to a custom SSIS component/tasks and update the Assembly Version, it seems to break my packages beyond repair, telling me it can't load the task:

Error loading Package1.dtsx: Error loading a task. The contact information for the task is "". This happens when loading a task fails.

All of the properties of said task now show:

Could not get value for property 'c-155-designer-name'. Specified cast is not valid.

Typically, a "breaking" change when it comes to code just means that you need to update your components to adhere to the new contract of the updated signatures. But with SSIS, it seems the only solution to this is to completely remove the component, and re-add the new version, and re-enter all of the property values/expressions. If I have a package containing 10 instances of a task that only had one property removed, for example, this results in a very time-consuming process of fixing my package.

So my questions:

1) Am I doing something wrong in my versioning/deployment that is causing my packages to unnecessarily break?

2) If this is just "by design" and the way it's meant to behave, what is the best practice for making breaking changes to custom tasks/components used by many packages? Should I just never change the assembly version, even when it is a breaking change (this seems to be less disastrous)?

3) As a last resort, if I'm stuck with having to fix the broken tasks, is there a better way to fix them rather than having to completely remove them, re-add them, and re-set all of their properties/expressions?

Thanks in advance.
Jerad