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 changes in
@theforeman/builder, it just was updated along with the other packages. Ths means that pinning to certain version ranges doesn’t behave as expected.
What is the reason for us updating all the packages together right now? More specifically, what I’m wondering is:
- Can we publish
@theforemanpackages independently to npm so they maintain their own semantic versioning?
- Can we define the relationships between
@theforemanpackages better so they don’t have to be updated together when one package was updated?