Ideally automation would exist to regenerate the packages on some cadence as new versions of genapi versions are taken. Improvements/changes to the tooling can cause previously generated code to be out of date.

Out of date code can cause noise as new packages are added because by default, dependencies are generated. More often than not dependencies already exist therefore changes to these packages show up in this workflow. Regenerating the packages on a regular cadence would eliminate this noise.

In a way it would be ideal if the packages were regenerated as part of the sdk dependency flows that update the genapi tooling version. This would be a good way to validate the incoming tooling update.