What's up with package.json in plugins?

[ekohl]

A previous related discussion on this topic:

Foreman-js - why keep all meta-packages on the same version?

For our foreman-js meta-packages (like @theforeman/vendor), I was told to update them all together when updating one, so in this PR, I updated @theforeman/test to 6.0.0, but needed to update the other @theforeman/* packages to 6.0.0 as well. Seeing something like katello-nightly-rpm-pipeline 756 failed makes me wonder if there is a way these can be updated independently. @theforeman/builder updated to 6.0.0, so Katello’s version was no longer available in packaging. But there were no breaking c…

The question there was never answered.