A lot of the updates for Cinnamon spices only affect some localization files. Except for their own language(s), users don't care about them and they're not needed.
Proposed solution: when checking for Spice updates, skip (or delay) localization updates that don't concern the user. Maybe check if the files edited in the commit actually match with the user's language(s). Then don't show the update as available (or just somehow indicate it's optional). The update can then be installed together with the first subsequent update that actually concerns the user (i.e. feature/bugfix/their own language).
This could also work if all translations contributed through e.g. GitHub PRs followed the same naming convention, so then you could just check the commit message (which the update manager already has access to).
I guess the language files could also be handled separately (i.e. not even downloaded) but that sounds way too complicated.
A lot of the updates for Cinnamon spices only affect some localization files. Except for their own language(s), users don't care about them and they're not needed.
Proposed solution: when checking for Spice updates, skip (or delay) localization updates that don't concern the user. Maybe check if the files edited in the commit actually match with the user's language(s). Then don't show the update as available (or just somehow indicate it's optional). The update can then be installed together with the first subsequent update that actually concerns the user (i.e. feature/bugfix/their own language).
This could also work if all translations contributed through e.g. GitHub PRs followed the same naming convention, so then you could just check the commit message (which the update manager already has access to).
I guess the language files could also be handled separately (i.e. not even downloaded) but that sounds way too complicated.